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

How can I divide default pairlist to multiple threads? #411

Open
roko772 opened this issue Aug 16, 2024 · 4 comments
Open

How can I divide default pairlist to multiple threads? #411

roko772 opened this issue Aug 16, 2024 · 4 comments

Comments

@roko772
Copy link

roko772 commented Aug 16, 2024

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?

@DominiqueGEORGES
Copy link

Hi.

I also have this error message, but it does not have any impact on the way NFI performs

@roko772
Copy link
Author

roko772 commented Aug 17, 2024

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 ;)

@DominiqueGEORGES
Copy link

Hi.

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.

I suggest you to wait till September ;-)

@roko772
Copy link
Author

roko772 commented Aug 24, 2024

For now perhaps I found a solution - according to frqetrade docs an OffsetFilter can be used.

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