@xyon126 Thank your for your reply! I kind of understand the logic in that, but I find it strange that this does not effect all EA's in the same way. Some EA's that take 1 second to test on one day of data also take roughly 300 seconds to test on 300 days of data, while other EA's slows down the strategy tester significantly depending on the duration of the testing period. I am trying to figure out if there is a way to structure the the code blocks to optimize the EA for testing faster, other than the usual things such as only running blocks when needed.
strategy tester slows down over time
-
Hi, has anyone else experienced that the mt5 strategy tester slows down over time. If I test 30 days on every tick it takes about 2-3 minutes to complete a test. If I use the same Ea with teh same settings and test 300 days it can take several hours to complete.
I wonder why this happpens, and if there is a way to sove it?
I am already structuring my EA's to run as fast as possible and only running code blocks when needed.
-
@piptheripper It has an overwhelming logic, the strategy tester is not instantaneous, depending on the time you want it to perform the test it may not slow down but take the necessary time that is not the same, example: How long does it take to mentally add 2 + 2 and 256985478 +254123595741? True, it does not take the same time because it is identical to the tester, you need to carry out the testing every day, if for one day you need 1 second for 300 days you will need 300 seconds.
-
@xyon126 Thank your for your reply! I kind of understand the logic in that, but I find it strange that this does not effect all EA's in the same way. Some EA's that take 1 second to test on one day of data also take roughly 300 seconds to test on 300 days of data, while other EA's slows down the strategy tester significantly depending on the duration of the testing period. I am trying to figure out if there is a way to structure the the code blocks to optimize the EA for testing faster, other than the usual things such as only running blocks when needed.
-
if you use trails, physical lines, and pending orders, it makes testing slow.