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

 
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.


Thanks Miguel for the quick reply, I have read all the comments in theis and referenced threads and my case is still not answered hence I posted here. Let me go in details:

- I have a 14700k which has 8 P cores, 8 HT threads and 12 E cores.

- MT5 Build 5200 (linux) only sees 16 core, earlier versions showed all 28 as possible agents.

- I use only local agents no local network farms nor cloud network.


I would expect to be able to decide how many of my cores to use for optimization on my own, even if HT cores are slower.

if I take the post you referenced I should see all my cores in Local, which is not the case. in monitoring it displays (see my 2nd attached image on the previous post) that 8 P cores are used (maybe HT cores are skipped), but out of my 12 available E cores only 8 are used, seemingly with the HT threads being not available as well, so the explanation doesn't add up.

 
Michael Charles Schefe #:

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.

Exactly what I am trying to express. I just want my threads back for myself. I really do not need MQL5 Cloud or to sell processor time there.

 
Máté Rémiás #:

Thanks Miguel for the quick reply, I have read all the comments in theis and referenced threads and my case is still not answered hence I posted here. Let me go in details:

- I have a 14700k which has 8 P cores, 8 HT threads and 12 E cores.

- MT5 Build 5200 (linux) only sees 16 core, earlier versions showed all 28 as possible agents.

- I use only local agents no local network farms nor cloud network.


I would expect to be able to decide how many of my cores to use for optimization on my own, even if HT cores are slower.

if I take the post you referenced I should see all my cores in Local, which is not the case. in monitoring it displays (see my 2nd attached image on the previous post) that 8 P cores are used (maybe HT cores are skipped), but out of my 12 available E cores only 8 are used, seemingly with the HT threads being not available as well, so the explanation doesn't add up.

You need to use the 'Local Network Farm'.

After the latest 5200 MT5 build update, in order to take advantage of all your processor's cores and threads in the Strategy Tester (locally), go to MT5 >> View >> Strategy Tester >> Agents >> Local Network Farm >> right click >> + Add >> Add Agents from Host (automatically) >> Next >> Done.


 
Eleni Anna Branou #:

You need to use the 'Local Network Farm'.

After the latest 5200 MT5 build update, in order to take advantage of all your processor's cores and threads in the Strategy Tester (locally), go to MT5 >> View >> Strategy Tester >> Agents >> Local Network Farm >> right click >> + Add >> Add Agents from Host (automatically) >> Next >> Done.

Thanks, Eleni! ❤️

 
Miguel Angel Vico Alba #:

Thanks, Eleni! ❤️

You're welcome Miguel. 😊

 
Eleni Anna Branou #:

You need to use the 'Local Network Farm'.

After the latest 5200 MT5 build update, in order to take advantage of all your processor's cores and threads in the Strategy Tester (locally), go to MT5 >> View >> Strategy Tester >> Agents >> Local Network Farm >> right click >> + Add >> Add Agents from Host (automatically) >> Next >> Done.


Thanks for your reply Eleni, unfortunately i don't see "Add Agents from Host (automatically)" option in my instance, see attached screenshot.

If I try to add agents from 127.0.0.1 (localhost) ports 3000-3023 the additional agents cannot be connected (only the already accessible Core 01-16), see second screenshot. These agents were available in previous version.

(sorry i could not figure out how to inline screenshots)
 
Máté Rémiás #:

Thanks for your reply Eleni, unfortunately i don't see "Add Agents from Host (automatically)" option in my instance, see attached screenshot.

If I try to add agents from 127.0.0.1 (localhost) ports 3000-3023 the additional agents cannot be connected (only the already accessible Core 01-16), see second screenshot. These agents were available in previous version.

Click 'Next' in your first screenshot.

 

We're still stuck at the same point. It no longer recognizes the E-cores. You can also see it in the Agents Manager where, in my case, it only detects the 6 P-cores. I've never used the cloud and I would like to go back to having my 20 local agents.

 
Massimo Peretto #:

We're still stuck at the same point. It no longer recognizes the E-cores. You can also see it in the Agents Manager where, in my case, it only detects the 6 P-cores. I've never used the cloud and I would like to go back to having my 20 local agents.

Regardless of how many cores are recognized, the optimization times are similar to those in older MT5 builds, when using both 'Local Agents' and 'Local Network Farm'.

I ran a well-known (to me) optimization that used to take about one hour in previous MT5 builds, and in build 5200 it finished in 1 hour and 2 minutes. This suggests that efficient cores may not have been utilized as much as we thought in earlier builds after all.

 
Unfortunately, I was only using local agents, so this is a real setback for me. Do you think the issue can be resolved, or do you believe the situation will remain as it is?