Local cores not helping in backtesting

New comment
 
I added the cores and i can some they show up on my local agents (some of them not all of them). When conducting the back test the status just alternates between connecting and ready they dont actually do any work. 

What am I missing here?
Files:
Cores_not_working.png  58 kb
 

A normal back-test (not optimisations) only uses one local thread/core for the test. It is not multi-thread/core, nor does it use the "farm".

Only when running optimisations will it use multiple threads/cores and "farm" agents if enabled.

 
Fernando Carreiro #:

A normal back-test (not optimisations) only uses one local thread/core for the test. It is not multi-thread/core, nor does it use the "farm".

Only when running optimisations will it use multiple threads/cores and "farm" agents if enabled.

I did not explain clearly, I am doing optimizations. I used to see all 32 cores, recently after an update it only shows 16 and I saw a thread that said i needed to add them locally. I have done that, not all the cores show up. On one instance (see attached photo) they cores are visible but they just bounce back from ready to connecting in the status 

 
Jeffrey James Travers #:

I did not explain clearly, I am doing optimizations. I used to see all 32 cores, recently after an update it only shows 16 and I saw a thread that said i needed to add them locally. I have done that, not all the cores show up. On one instance (see attached photo) they cores are visible but they just bounce back from ready to connecting in the status 

In the latest 5260 MT5 build, all previously shown local cores (before 5200 build) are visible and can be used again.

 
Eleni Anna Branou #:

In the latest 5260 MT5 build, all previously shown local cores (before 5200 build) are visible and can be used agai

You are an absolute gem. TY!

New comment