MT5 issues after update: CPU agent(core) reduced from 16 to 8 - page 2

 
Eleni Anna Branou #:

Hmm, I've done that Alain, but on my computer doesn't seem to work, the optimization doesn't start at all.

It works fine with 'Local Agents' enabled at similar times as before the 5200 update.

Maybe it has to do with the fact that I have the hybrid Intel Ultra 9-185H processor.

https://www.mql5.com/ru/forum/492248/page3#comment_57712506

Just as a quick summary of the link shared:

  • In local tests, you can use all logical cores (physical + HT).
  • In the MQL5 Cloud Network, only real physical cores are used (neither HT nor LP).
  • This is by design, to avoid using weak threads that would reduce overall performance.

Thanks Eleni!

 
None of the proposed solutions works for me. I don’t see how leaving eight threads idle benefits me.

My conclusion is that MetaTrader 5’s latest update mishandles/underutilizes  my Intel Core i9-12900H’s hybrid design, which has six Performance-cores (P-cores) and eight Efficient-cores (E-cores). It ignores the E-cores and caps the Strategy Tester at the 12 P-core threads instead of the full 20, cutting my optimization power nearly in half.

That leaves me with little choice but to sell the laptop and switch to an AMD Ryzen 9, whose uniform cores MT5 will fully recognize and use for true multi-threaded backtesting and optimization.

I may also buy a used computer to run on my network and boost the total cores available.

 

For me only 16 cores are visible out of the 28 available and they are mostly E cores (16-27) and some P cores (0-15) of my cpu.

If i try to use local network farm i see only the same 16 cores. In the previous versions I saw all 28 cores, this is definitely a step back in performance.

I am on linux.

 
Máté Rémiás # : If i try to use local network farm i see only the same 16 cores. In the previous versions I saw all 28 cores, this is definitely a step back in performance.

This topic has already been explained in detail earlier in the thread, but I'll paste the relevant part here so you can review it directly.

Forum on trading, automated trading systems and testing of trading strategies

New MetaTrader 5 platform version build 5200: OpenBLAS extension and increased control in MQL5

Renat Fatkhullin , 2025.08.03 15:50

For internal tests inside the terminal, you are shown all 32 cores (physical + hyperthreading). Some processors also have Efficient Low Power, which are always ignored by the terminal and agents. LP cores (not to be confused with multi-core) are practically useless and are not even used by the operating system in normal mode. LP cores simply mislead people on hybrid processors such as Intel Core Ultra 185H :

Total Cores                       16

# of Performance-cores            6
# of Efficient-cores              8
# of Low Power Efficient-cores    2

Total Threads                     22 

You see and can use in your case all 32 cores as local agents on 14900K.

But in MQL5 Cloud we only accept physical cores (16).


To make everything as clear as possible:

  1. CPU manufacturers are making Hyperthreading cores and chasing the number
  2. In fact, hyperthreading at the limit gives +20% performance when the number of cores is doubled (+100%)
  3. Buyers are deluding themselves when they buy such cores and expect increased performance.
  4. There are no restrictions on using such hyperthreading cores in your terminal (but this is often clearly unprofitable due to the lack of memory for +100% of non-cores)
  5. MQL5 Cloud does not deceive itself - it has no need to accept obviously slow cores, paying for their weak work

 
Máté Rémiás #:

For me only 16 cores are visible out of the 28 available and they are mostly E cores (16-27) and some P cores (0-15) of my cpu.

If i try to use local network farm i see only the same 16 cores. In the previous versions I saw all 28 cores, this is definitely a step back in performance.

I am on linux.

As I understand your processor has 8 Performance-cores. You see 2 threads per core. The 12 e-cores stay idle and are ignored by MT5. I don't know why they did this. 

 
Miguel Angel Vico Alba #:

This topic has already been explained in detail earlier in the thread, but I'll paste the relevant part here so you can review it directly.


Well, I want to use for my optimizations everything I have. Since the update it is very clear how much slow it became. I don't care for getting peanuts selling my processor time.
The new update does not allow me to use the extra power my computer has. Even if it was as low as 5%, which is not, I would like to use that. MQL5 is just doing this because the majority of people don't even know how to optimize and backtest.

 
A V #MQL5 is just doing this because the majority of people don't even know how to optimize and backtest.

Forum on trading, automated trading systems and testing of trading strategies

New MetaTrader 5 platform version build 5200: OpenBLAS extension and increased control in MQL5

Renat Fatkhullin , 2025.08.03 15:50

MQL5 Cloud does not deceive itself - it has no need to accept obviously slow cores, paying for their weak work

 
Miguel Angel Vico Alba #:

Nor do we need to sell our processor time for virtually nothing. I just want to use all my processor power myself.
I just optimize things that deserve that. I do not care for testing or optimizing developers' work who are only taking advantage of MQL5 users to sell crap.
Just unlock my processors to myself and I will commit to never try to sell my processor time to anyone.

 
A V #:

Nor do we need to sell our processor time for virtually nothing. I just want to use all my processor power myself.
I just optimize things that deserve that. I do not care for testing or optimizing developers' work who are only taking advantage of MQL5 users to sell crap.
Just unlock my processors to myself and I will commit to never try to sell my processor time to anyone.

Developers who are using MQL Cloud to optimize their work, are either already rich or are doing subpar development and using poor OHLC data to lure buyers.

 
Miguel Angel Vico Alba #:

Come on Miguel! how long have you been doing optimiser or backtests? with every 2nd update, more cpus are crippled. The justification that you and developers use mentions the use of the cloud, but most devs do not use the cloud. Give us the use of our own computers and maximum cpu usage of our own computers. The devs can make mt5 to detect if the cloud is enabled, therefore they can then limit the cpus as they like, but for personal and local use, give us full use of our cpus.