Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using only one CPU core #444

Open
seventhsite opened this issue Nov 23, 2024 · 1 comment
Open

Using only one CPU core #444

seventhsite opened this issue Nov 23, 2024 · 1 comment

Comments

@seventhsite
Copy link
Contributor

Hi!
I use all default configs downloaded from this git in 3 fregtrade docker containers live.
Sometimes I see when one or more processes use 100% of one processor core.

Screenshot from 2024-11-23 17-20-48

I don't see any errors, like "Outdated history for pair..." or "Strategy analysis took..." I just want to ask if this is normal behavior, that there is no parallelization across cores? Or should I think about switching to a more powerful processor with a higher frequency per core? Now I use Hetzner VPS on ARM Ampere Altra CPU.

@HeimLabor
Copy link

Yes, this is normal behavior. Freqtrade runs on a single core due to Python's Global Interpreter Lock (GIL). Computational intensive strategies, such as NostalgiaForInfinity, which rely on multiple indicators and historical data, can cause spikes to 100% on one core, especially during indicator calculations.

However, this typically has no significant impact because trading strategies like NostalgiaForInfinity don't rely on millisecond-level precision. The bot operates on candle intervals (e.g., 5 minutes), so slight delays during processing usually don't significantly affect trade execution or performance.

Switching to a CPU with higher single-core performance may help if the load causes noticeable delays, but as you mentioned, nothing appears in the error logs. I tested this on an i9-13900H and also observed occasional spikes to 100% on the utilized single core.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants