Hi there,
Running Win7 Pro on an i7 2600K with splat .08 - 16gb of ram.

I've had hyperthreading disabled on this PC because I have an old XP partition with GigaStudio3 on it and GS didn't play well with hyper threading. Now that I'm not using GS3 anymore I'm wondering if there's any perk to enabling hyper threading?

Somewhat typical usage for me is running 4 to 5 instances of Kontakt and sometimes Omnisphere 2.
I'm not seeing any performance issues with it off but it might be nice to get a tiny bit more headroom if possible.

Thanks!

I believe that with Sonar, enabling hyper threading on your RIG will in essence give you twice the horse power.  Definitely worth trying to see.
 
I have a 6 core machine with hyper threading enabled which gives me 12 threads.... my system pretty much screams.  No issues with CPU juice.  I run many instances of KONTAKT without any issues and a ton of UAD and native plugins with my projects.
 
I have since gone to 96K projects without to much increased load on my processors.  The latest version of SPLAT has spread the CPU load more evenly over available threads and seems to have made the system even better.  
 
Can't hurt to try.

thanks jimkleban

I'll give it a try.

the number of threads is secondary to the processor clock speed. I've read Jim Roseberry having said that many times.

mudgel
the number of threads is secondary to the processor clock speed. I've read Jim Roseberry having said that many times.

This is also what I've heard (from Jim as well) .It also helped me choose the CPU im using now.

I too have heard that processor speed is important but if you already have a processor that supports multi threading, are you sure it is wise to turn it off.  Seems to me, unless turning it off increases the CPU speed, it would make sense to turn hyper threading on, no? Especially since CAKEWALK has refined and evolved the multi thread processing so well?
 
Just asking,
Jim

jimkleban
I too have heard that processor speed is important but if you already have a processor that supports multi threading, are you sure it is wise to turn it off.  Seems to me, unless turning it off increases the CPU speed, it would make sense to turn hyper threading on, no? Especially since CAKEWALK has refined and evolved the multi thread processing so well?
 
Just asking,
Jim

good question

Steve_Karl

jimkleban
I too have heard that processor speed is important but if you already have a processor that supports multi threading, are you sure it is wise to turn it off.  Seems to me, unless turning it off increases the CPU speed, it would make sense to turn hyper threading on, no? Especially since CAKEWALK has refined and evolved the multi thread processing so well?
 
Just asking,
Jim

good question

My understanding is that a thread can only run on one core at a time, thus performance is limited to the clock speed of an individual core. You can't run any faster than the CPU frequency of one core.
 
Oversimplification: Enabling multi threading lets the processor take advantage of scheduling an additional thread to run on a core, creating a virtual second core, that can execute during the brief moments when the pipeline is waiting for something to do.  It makes more efficient use of the available CPU cycles.  A thread isn't always 100% busy in the CPU, it sometimes has to wait on read/writes from RAM or disk, etc.  A quad-core without hyper-threading would perform slightly slower under average use than a quad core with eight virtual cores enabled via hyper-threading.
 
My opinion, is turn it on.  Sonar has supported multi-threading, multi-core for many versions now, and they keep improving it.  For example, with the recent plug-in load leveling.
 
Ultimately it is up to the application to be multi-thread aware, and to intelligently break it's workload down into multiple threads to take advantage of the hardware capabilities.  That is why you can see old applications suck one core dry sometimes.

I disabled multi-threading. Here is why:
Like the OP pointed out, there is just a virtual second instance of the core. the idea is to provide work for the cpu, even when a thread is waiting for e.g. the disk i.o.
Using a DAW there is not the problem to provide enough load to a cpu, the main issue is to finish a task before the buffer runs dry.
Additional (virtualized) cores creates additional administrative work for the shedulers, but you will not get more "bang" from the cpu. It is just easier to max out each core. If the throughput is prio 1 then this strategy is great. If the response time of the system is prio 1, then it is not.
Since I disabled multithreading, the count of drop outs and glitches was down in a significant amount (with my old interface).
 
Just try it. I am sure, that the administrative overhead for the cpu, the OS and SONAR have negative impact. If you observe bad core utilization, use multi-threading again...  
 

So much fail in these responses......WOW!
 
First of all, while it is true that a 4GHz single core would outperform a 2GHz dual core, in a modern OS with a modern application like Sonar, multi-threading works quite efficiently, especially in inherently parallel tasks like a multi-track DAW.
 
What happens with HYPER-threading is that the CPU is allowed to process two thread on 1 core, using different parts of its pipeline at the same time (think Floating Point versus Integer). It certainly doesn't double the performance of a core, but can lead to 20% more throughput. There IS more scheduling overhead, but not very much and the performance increase in highly mixed workloads is noticeable. For instance, the screen rendering parts of Sonar are very much integer tasks, while calculating plugin processing is highly Floating Point based.