You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm doing a dry runs of NFIX4 on VM in my NAS with i5-6600 - made access to all 4 cores to the VM already, but my target platform is RPi 3B+.
I'm getting calculation time warning: 2024-08-16 04:57:54 WARNING freqtrade.freqtradebot - Strategy analysis took 171.78s, more than 25% of the timeframe (75.00s). This can lead to delayed orders and missed signals.Consider either reducing the amount of work your strategy performs or reduce the amount of pairs in the Pairlist.
Now I understand, that 75 pairs stated in pairlist-volume-binance-usdt.json is too much for my NAS, and 3B+ is probably unable to run this strat, but it's utilizing only one thread, and both devices had four of them.
Here's my question - can I divide the pairlist and run multiple simultaneous instances with it? What is the best method?
The text was updated successfully, but these errors were encountered:
Still, I want to fix it, not only because it's not recommended, but also because "I paid for the whole speedometer, so I'll use the whole speedometer". In my case, I paid for all four cores ;)
A new version is foreseen for next week, priority is set on it.
You should be able to reduce the list, but I don't know how to split over more than 1 bot.
Hi, I'm doing a dry runs of NFIX4 on VM in my NAS with i5-6600 - made access to all 4 cores to the VM already, but my target platform is RPi 3B+.
I'm getting calculation time warning:
2024-08-16 04:57:54 WARNING freqtrade.freqtradebot - Strategy analysis took 171.78s, more than 25% of the timeframe (75.00s). This can lead to delayed orders and missed signals.Consider either reducing the amount of work your strategy performs or reduce the amount of pairs in the Pairlist.
Now I understand, that 75 pairs stated in pairlist-volume-binance-usdt.json is too much for my NAS, and 3B+ is probably unable to run this strat, but it's utilizing only one thread, and both devices had four of them.
Here's my question - can I divide the pairlist and run multiple simultaneous instances with it? What is the best method?
The text was updated successfully, but these errors were encountered: