September 3, 2020 at 22:57 #59352
I ve noticed that both Generator and Reactor speed had slowed down considerably in comparison to few months ago. I only run once instance of EA studio and over a course of 24hrs I am getting maybe a few thousand startegies generated as oppose to couple of hundered thousand back in May this year. What could be a reason for that?
September 4, 2020 at 6:51 #59357
Glad to hear from you. Actually EA Studio got faster…there was an update which made it much faster.
The reason it might get slower with you is if you use a huge Historical data.
How many bars do you use?
September 4, 2020 at 12:06 #59360
I have approx 20 instruments with 200000 bars data each. Is it worth deleting the data for pairs I don’t use?
September 4, 2020 at 21:33 #59363
Deleting history data for unused instruments didn’t work…
September 5, 2020 at 7:14 #59365
No, I meant something different.
If you use M15 for example, how many bars do you see in your Historical data?
Let’s say you use about 30 000 bars. The generator would work 2 times slower if you use 60 000. If you use 120 000 it will become 4 times slower.
Recently, I realized that there is no point in using more than 50 000 bars on any of the time frames.
When I use fewer bars the generator works much faster and the strategies are more active.
September 5, 2020 at 12:23 #59368
Indeed, I can see a significant difference in number of strategies calculated if only use 30000 of bars. Somehow I was convinced the more history bars the better.
Do you still find most succesful ones on M15 – M60 timeframes?
September 9, 2020 at 14:21 #59606
I am glad to hear from you. To be honest, I used to believe the same – the more data, the better. But with the time, I saw that the generator is capable of finding robust strategies with many counts of trades, even if we use a small number of bars. And that is better for me.
We have more active strategies this way, and at the same time, we depend more on the recent data.
And of course, the generator works much faster 🙂
- You must be logged in to reply to this topic.