Hello everyone.
I would also like to contribute something to analyzing the error.
Because I have had this problem for a while.
I only use Metatrader5.
My EA consists of 162 blocks and includes 3 timeframes and account queries.
1.
When optimizing with real ticks, the optimization stops and the following error is displayed. Optimization from 01/01/2020
“tested with error "no memory for ticks generating (test events error)"
During live trading, with fast ticks and only one EA, the CPU rose to 100%
The problem was the long code and nesting when updating.
With 1min OHLC, the optimization works.
I revised the EA and use the “once per minutes” block before each tree with multiple blocks.
Now the optimization worked for real tick and live trading.
In the backtest there was only a small deviation between the EA with on ticks and once per minutes.
- After a small change to the EA, the optimization did not work again.
Now I have created the EA once with fxDreema. And once via the Metatrader Editor (compilation).
I found that the file of the EA in fxdreema is larger than the EA in the Metatrader Editor. The results in the backtest are identical.
The backtest in the Metatrader Editor ran about 50% faster.
When optimizing only 16 tasks, the EA generated by Metatrader worked. The EA generated by fxdreema did not work.
With more than 16 tasks during optimization, the EA generated by Metatrader no longer worked either.
Now I have carried out a test on a different computer.
Previous PC:
16 GB RAM and 4 threads
Second PC:
32 GB and 12 threads
Now the optimization worked with real ticks and 640 tasks during optimization, without any problems.
CONCLUSION
Currently, the PC is the weakest link when it comes to optimizing MT5 with real ticks.
I think fxdreema is a great structured program for logical programming.
I am aware that fxdreema has to generate a much longer code than a hand-programmed EA. This is also the case with competing programs.
But it still has to be applicable.
Perhaps fxdreema can say something about it itself.
Otherwise, I would send the text to support again.
Perhaps it would be possible to provide a list of which blocks and their links should be avoided.
And which ones use the most resources, such as loops and account queries over a longer period of time.
Best regards
Lacone