Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations cowski on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!
How bad is the performance hit with hyperthreading enabled?
- Thread starter Tingsryd
- Start date
My guess is you would not notice it since NX is not multithreaded in most of the sub applications so you are getting 100% of that core process. Drawing view generation, NC machining and stress analysis are so you may notice some slow down as the process has to keep track of the processes.
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli
I've not double checked actual figures in a while, however, previously I found a serious hit in performance with hyper-threading.
This is because the majority of commands in NX are not multi thread.
Hyper-threading effectively divides the cores of your processor in half.
If you look in windows task manager, when you turn on hyper-threading in your bios your processor count doubles.
This means that NX can only use 1/2 a processor core for most of its operations.
Would be interested to hear if anyone has done any benchmarking more recently (think mine was in NX6).
Mark Benson
Aerodynamic Model Designer
To a Designer, the glass was right on CAD.
This is because the majority of commands in NX are not multi thread.
Hyper-threading effectively divides the cores of your processor in half.
If you look in windows task manager, when you turn on hyper-threading in your bios your processor count doubles.
This means that NX can only use 1/2 a processor core for most of its operations.
Would be interested to hear if anyone has done any benchmarking more recently (think mine was in NX6).
Mark Benson
Aerodynamic Model Designer
To a Designer, the glass was right on CAD.
- Thread starter
- #4
From what I heard NX was not written for hyperthreading which is different from multithreading. However there are a number of areas where NX is multithreaded such as boolean functions, silhouetting, sim, manufacturing and more. I love seeing NX pegging cores to 100%! NX cam has added a lot of multithreading and more is added every release.
11.0.2
11.0.2
Hyper threading is just a way for the processor to 'fool' the OS in thinking it has twice as many cores. It splits the CPU into 2 virtual cores and reduces the amount these cores can process to roughly 1/2 of the original CPU. This is great if your programs can use multiple cores.
To use multiple cores you need to program with multiple threads.
Not all features in NX use multiple threads and therefore can only use a single core.
Historically not that many functions/features in NX were multi threaded so I've always advised turning hyper-threading off.
Multi-Core and multi-threading
Hyper-threading
Mark Benson
Aerodynamic Model Designer
To a Designer, the glass was right on CAD.
To use multiple cores you need to program with multiple threads.
Not all features in NX use multiple threads and therefore can only use a single core.
Historically not that many functions/features in NX were multi threaded so I've always advised turning hyper-threading off.
Multi-Core and multi-threading
Hyper-threading
Mark Benson
Aerodynamic Model Designer
To a Designer, the glass was right on CAD.
- Thread starter
- #6
Even though there is plenty in NX which is multithreaded for our purposes, I leave hyperthreading off on all our workstation because NX is not written to use hyperthreading.
Update,
I just found the docs pertaining to hyperthreading...
Hyper-Threading on Intel Processors
Some Intel processors provide a Hyper-Threading feature in which a single processor can support multiple instructions, thus emulating additional processor cores. When Hyper-Threading is enabled, it can lead to a conflict with threading within NX Nastran for both SMP and DMP executables. Hyper-Threading should be disabled, which can be done permanently through BIOS operations.
11.0.2
Update,
I just found the docs pertaining to hyperthreading...
Hyper-Threading on Intel Processors
Some Intel processors provide a Hyper-Threading feature in which a single processor can support multiple instructions, thus emulating additional processor cores. When Hyper-Threading is enabled, it can lead to a conflict with threading within NX Nastran for both SMP and DMP executables. Hyper-Threading should be disabled, which can be done permanently through BIOS operations.
11.0.2
- Status
Similar threads
- Locked
- Question
- Locked
- Question
