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

Strategy analysis took 178.11s, more than 25% of the timeframe (75.00s) #412

Open
riven-blade opened this issue Aug 16, 2024 · 7 comments
Open

Comments

@riven-blade
Copy link

WARNING - Strategy analysis took 178.11s, 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.

@DominiqueGEORGES
Copy link

Hi.

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

@riven-blade
Copy link
Author

Hi.
Are you sure ?
This will have a great impact on the ultra-short term. The NFI trading cycle is relatively long, but I am not sure whether it will affect the ultra-short term.

@stash86
Copy link
Contributor

stash86 commented Aug 17, 2024

Imagine you have a green long candles. By the time you entered, you might be entering near the top of that green candle. Decide yourself whether buying near the top is good or not.

@iterativv
Copy link
Owner

Hi. Are you sure ? This will have a great impact on the ultra-short term. The NFI trading cycle is relatively long, but I am not sure whether it will affect the ultra-short term.

Hi, in long term it doesn't matter. Some times it's better to delay some times is better to be faster.

There will be a new version, that for this part at least, is going to use all cores. Live ready in 2-3 weeks now.

@roko772
Copy link

roko772 commented Aug 17, 2024

There will be a new version, that for this part at least, is going to use all cores. Live ready in 2-3 weeks now.

Nobody asked, everybody needed - that's all I can say. Thank you!

@roko772
Copy link

roko772 commented Aug 24, 2024

Perhaps an OffsetFilter can be used to divide pairlist between multiple instances.

@iterativv
Copy link
Owner

Perhaps an OffsetFilter can be used to divide pairlist between multiple instances.

Yes, that been done. Anyway, there will be no issues with CPU usage for X5. In 2-3 weeks should be ready for the first live runs.

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

5 participants