Problem using workers with DIAdem 2014

[JuliaDawkins]

Hi, I have two laptops, one that is dual core with HT, so "SystemInfo.CPUCount" returns 4, and another with 4 cores with HT and "SystemInfo.CPUCount" returns 8. So I'll refer to these as my 4-core and 8-core laptops.

I'm testing using worker objects for a project, and my 4-core laptop does not perform well with workers, and I'm not sure how to look into this.  It actually performs much worse than running everything in my native instance of DIAdem (100 seconds vs. 40 seconds).  My 8-core laptop performs well and pretty much as expected I think.

The script I'm using is in my attached zip file called "10SecondsAllCores.VBS".  The attached PNG files show my view in DebugView for my 4- and 8-core machines.  As you can see it takes a long time for each worker to start in the 4-core machine (about 20 seconds).  The total script time for "10SecondsAllCores.VBS" for my 4-core machine is 100 seconds, and 17 for my 8-core machine.

Is there perhaps some setting in my 4-core machine that is causing this?  I appreciate any help you can offer!

Julia

[Christian-P]

Hey Julia,

I did some testing with DIAdem 2014 and 2015 SP2 32 Bit on my 4 core machine.

On my machine all workers can be created and started in 1.4 sec (see attached log).

It looks suspicious that creating the workers takes very long according to your screenshots...

Are you using an SSD in your machine? Just an idea, because it could take longer on a non SSD system to start new DIAdem engines in the background.

Once every worker is running there should be a performance benefit compared to only one script engine running.

Regards

[JuliaDawkins]

Thanks for the response!  I tried the same script with DIAdem 2017 and it runs just fine, all 4 workers are created and started in 0.85 seconds! But DIAdem 2014 is much slower for some reason on this particular computer.  I am not using an SSD 😞 Hopefully this is just this computer and I will test on other computers that require DIAdem 2014...