"sim_run_num_threads" config option misbehaving?

[JonathanHodgson]

Has anyone else played with this?  It doesn't appear to work quite as intended...

sim_run_num_threads 1 does indeed run one thread.

sim_run_num_threads 2 runs two threads and displays

Parallel Processing Status

   Parallel task limit for current run:            2

   Parallel task limit for current platform:      64

   Number of processors detected automatically:    8

All the other options (half, all_but_2, all_but_1, all) appear to run on the full 8 cores (4 physical with hyperthreading):

Parallel Processing Status

   Parallel task limit for current run:            8

   Parallel task limit for current platform:      64

   Number of processors detected automatically:    8

Are these options being compared to the 'platform' limit of 64, perhaps?

Creo 2.0, M120.

This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[JonathanHodgson · Accepted solution]

Reproduced by PTC (within an hour or two!), and reported to R&D as SPR 4833736.

The workaround is to use the Windows environment variable (not config option) MEC_NUM_THREADS.

This appears to be the old version of the option, but is the one that works!

PC specification for Mechanica

[DenisJaunin]

Hello,

There is some information on the following links.

Best regards.

Denis.

Mech WF2.0 with Multiple Processors

https://msdn.microsoft.com/fr-fr/library/yw6c0z19.aspx

[JonathanHodgson]

Thanks Denis - although I don't understand the relevance of the Microsoft link to a PTC product.

sim_run_num_threads is the option that is now documented in the Help (and doesn't work as expected); the thread I linked (dated 2009) suggested that MEC_NUM_THREADS was for "older versions" of the software, so I shouldn't be having to use it in Creo 2.0 (although it's useful that it still works).