CPU performance with multi-threads?

[shane]

While most of synth work has traditionally been hardware, I've been working more with VST instruments (Serum 2, mostly) and noticing something with Sonar: VST instruments seem to get directed to the same CPU, at least according to the Performance Meter. See picture. 

(This is with 10 VST instruments including Serum2, Waldorf Microwave, NI Maschine 3, GForce TVS Pro, Korg ARP Odyssey/2600)

This causes CPU hogs like Serum to choke quite a bit-- sometimes simply scrolling thru presets makes the audio engine stop and at the same time, that CPU spikes in the Performance Meter.  Disabling/deleting Serum doesn't make the spike go down much, if any at all. In fact, none of the VST's removal show that they are the CPU culprit. 

Is this expected? Is there a way to correct it in my settings or preferences that I've missed? 
I would expect it to be more leveled out. I double checked with my production partner, and he has an Intel chip that maintains level performance with VST's. 

 

My system: 

Windows 10

Dual Intel Xeon Platinum 8176 @2.1Ghz = Dual 56 cores = 112 Cores. 

96 GB RAM

 

Edited Saturday at 05:20 PM by shane

[Glenn Stanton]

not sure if this is helpful. for Serum2 - https://splice.com/blog/optimizing-serum-cpu-efficiency/ and it may be similar for other - not so much multi-core as they should be. 

[Wookiee]

@shane it may be worth your time to do a fodum search, use chrome or other browser serach engine, Noel did an extensive explanation of how Sonar handles multi threading. Inparticular with regards to P & E cores and audio threads, not that this CPU has E cores. I am sure it applies to both win 10 & 11 but..... Do you have plugin load balancing enabled

Having looked at the Intel Ark for your CPU it is classed as a Server CPU rather than workstation and its maximum clock is quite slow at 3.8 compared with modern 5.n + clock speeds. Whilst it has lots of available threads basic raw grunt is lacking compared to modern workstation CPU's.