My first MT5 optimization on fxDreema...and the fisrt issue!

[l'andorrà]

I'm trying to optimize the first bot created with fxDreema on MT5 and something weird happens. I optimized many non fxDreema bots in the past so I can confirm the problem is not the platform itself nor the available data. I'm using that same data to optimize the bot.

The issue is that when I click on 'Start', the number of tasks per core is correctly distributed...but none of them is executed! I waited for a whole day to see if maybe the needed more time than usual, but nothing changed.

The task manager is showing 48% of RAM memory RAM is being used and 99-100% CPU capacity is used. And this is what I see:

It stays there for hours and that's it! Honestly I don't know what to think and I have no idea why not a single result is found.

Any suggestions?

[sktsec]

The process might be too low to observe. I had similar experience in MT5.
I am still feeling strange that it is slow in backtesting even a simple EA., with Its 64bit, multithread capacity.

[tomaszkva]

I create my first bot in this website. And I facing this problem . I cant run optimization. I Made really not difficult strategy and when I save the mql5 file I got shock. 12.000 lines why is so long this is just a really few things. Before I was write more difficult strategy not was more than 700 lines. Im not happy. I can imagine if I create here some more difficult strategy it will 3.000.000 lines

[l'andorrà]

Man, this is so frustratingly disappointing. Hasn't anyone found this issue before?

[sktsec]

@l-andorrà
Exact reason not known. I had made a bot in MT5 with a simple custom indicator (composed of 2 MAs only) with clear buy / sell signals. But the situation was similar to yours.

The optimizaion/backtesting was very very slow. I thought it was impossible but had no way to fix it.

Maybe a shorter period can help.

[OntradingX]

@l-andorrà
You can share the Settings tab screen to see more information, for example:

1. What model are you using?
2. Which period is optimizing.
3. How many inputs are optimizing and how many steps are being consumed.

All of this makes a huge difference when optimizing because the longer the time and the greater the amount of data to be optimized, the longer the processing time will be for it to find results.

The MT5 optimizer works very well, but there are many steps to be analyzed internally in MT5 and also in your EA in terms of parameters.

I believe that most people develop EA's and want to test in OHLC, but the correct thing is to test in Each tick based on a real tick, but it is also necessary to analyze in your EA where to place the blocks (once per bar), currently I use it in practically every my EA and all my strategies this block and only in the management part I do not allow the use of it, as it is necessary to check (at each tick) trailings and money information, so what I want to say briefly is that all its logic it has to be well thought out so as not to overload optimization through MT5.

Another very important detail is that it is necessary to clean internal data from the Terminal and Tester folders, internally there is data that is saved from previous optimizations or from symbols that were downloaded during previous backtests and this consumes space on your disk. (Optimization takes up disk space).

Use Folder Size program free to scan

[l'andorrà]

@OntradingX Thank you very much for your insight. Definitely I need to review all those parameters. I'm just surprised because this is the first time I tried this on MT5.

[Jaico]

También puede ser que la optimización no arroje mejoras datos que los que usas por defecto. a mi me paso también con un ea y llegue a esa conclusión.

[l'andorrà]

@Jaico Me temo que no. Cuando más indgo más veo que el problema está en los bucles usados en fxDreema. Son una auténtica pesadilla para el optimizador. Pero gracias por tu sugerencia.

[OntradingX]

@l-andorrà I believe that Fxdreema also contributes to the slowness, but on the other hand I think that the logic involved in the projects also causes the slowness, for a while now I started to optimize my EA's which are huge in number of blocks and the adapt my strategies to open orders when (closing) the candles using the block (once per bar) and I realized that this, in addition to helping with optimization so that it becomes faster, improved my entire logic, currently most of my EA's I focus on Always look at the bar closing to avoid frustration with slowness.

[OntradingX]

Look at this project I made recently, it has a lot of blocks and is super fast in backtests

[jstap]

As a basic rule only have the ea doing something when needed, then there is the tabs, a lot can be done on chart so when something happens, it doesn't work on backtest (unless MT5)

[OntradingX]

@jstap said in My first MT5 optimization on fxDreema...and the fisrt issue!:

basic rule only have the ea doing something when needed

I like this " basic rule only have the ea doing something when needed " great words

[Ipod]

I had this problem once, it was a long time ago though but If I remember correctly it was solved by exporting the EA to mql5 and investigating in the MT5 terminal directly. Specifically compiling in MT5 which shows many errors, usually doubles being converted to int and vice versa but it might show some error or logic issue that can be resolved.

Try resolving as many conflicts as possible and trying again, also ensure MT5 is updated correctly. There was a fault a while ago where MT5 would hang forever due to using the cores incorrectly (is the CPU running @ 100% all the time?, raising a ticket and sending logs to the mql5 website might help but also just looking into the logs in your terminal can help.

• Check task manager for high cpu or maxed out ram first, reduce cores or reduce date range if ram is filling up.
• Check terminal logs from the tester
• Export to MT5 and fix compiling errors
• Raise a ticket in mql5 if nothing is found
• If you are running long term real tick tests that also could be the problem as it can take forever to test that amount of data.

If you want me to check your logs, ea code, etc i am happy to help but that is something you might / probably wont want to do.

[l'andorrà]

@OntradingX The problem is not backtest, but optimization. I have no problem with huge projects when backtesting. The issue is optimizing them.

[l'andorrà]

@Ipod The bot works perfectly fine. And it works smoothly when backtested. The problem is optimizing it.

[OntradingX]

@l-andorrà I understand, the steps I mentioned really helped me to solve slow problems when optimizing robots, before when I didn't create a well-elaborated logic thinking from the beginning about future optimizations, when I was going to perform optimization, the same thing happened to me, to perform the tasks. it was an eternity.
But it is difficult to help you without at least having access to what you are actually doing, perhaps something in the middle of your project is causing this problem, my suggestion is that you review your entire project or create a new project and copy and by pasting parts of the blocks and testing to see when this is happening, perhaps this is a way of locating at which point you can apply a logic change to your EA.

[Ipod]

@l-andorrà I know the problem is with optmising, I had this problem a long time ago too.

Did you try anything I mentioned, even the logs?

Ask for help, and then continue to ignore everything people say or suggest.

[l'andorrà]

@OntradingX Yes, that is exactly what I'm doing now, and it is painfully slow and boring!

[l'andorrà]

@Ipod I, definitely searching for ways to improve the logic, so I will stop whining here and get my shit done! Thank you very much for your help and kind words.