duration of test periods with fxdreema?
-
Does anyone have experience with the test periods of the MT4 tester:
When I'm programming an EA in MT4-editor and the other EA was made with fxdreema.
How big are the differences in the in the duration of the test periods for the ea that was created with the MT4-editor and the ea that was created with fxdreema?I ask this because I wonder. I have two ea 's. The one has a trial period of three hours. The other has a test duration of 600 up to 1200 hours....same timeframe, same data, all the same.
-
EAs created with fxDreema does not have trial period normally. There is small option in "Project Options", but it is empty and inactive by default.
-
Why does it take a very long time to test an ea that was created with fxdreema?
-
Let's define what "trial period" means. So you are talking about the time needed for an EA to be backtested? If this is the case, I can expect EA created with fxDreema to be the slowest one of both, because fxDreema was made in a way to support various strategies and there are extra things in every block that can slow down testing. For example, block parameters - there are blocks with many input parameters and when such a block is executed it checks those parameters. Or if "on Trade" is used, because it is not native for MetaTrader 4. And it also depends on how the strategy was built, what blocks are used and how often are they executed. I beleive it's possible to make things faster, I am already aware of some things that slows down the process, but a well designed custom made EA will always be a bit faster.
-
Ok, I will send you an ea as private message. Can you revaluate why the test duration in the MT4 tester is so long?
-
Sure, let's see it.
-
Thank you for the chatting but the problems exits further on. I wrote you an e-mail with the following contents:
We have chate together. I have improved and simplified the ea for the optimizing in the tester. The problem that this very simple ea takes a long long time for the optimation prozess exits further on. I have this problem with a lot ea´s that was created with the latest version local version.
After optimationstep 3 the tester has displayed 2:66 hours optimationtime but stops to count higher.
I have canceled the running optimation after 6 minutes and 12 seconds. The optimationtime 180 hours was displayed by the tester:
If I keep running the tester for 60 minutes the optimationtime 1850 hours was displayed by the tester.
Can you please check of errors with the code. I have no answers what it is? I am not a programmer.
I attached the 2 files.
