Quote:
I've compared the final release build (9.40) against 9.37 and I don't see any difference in CPU usage - well, _maybe_ 9.40 uses 1% more, but it's a bit hard to see the exact numbers. Also, I've loaded an old preset and turned all "Dynamic" speeds on, and that also gave about a 1% increase in CPU usage.
What differences are you seeing?
Note: If you've configured it to use a specific core, that is now (by default) a "preferrerd" instead of "forced" core. Meaning that Windows can, if it needs to, move it somewhere else. I've done tests and this turned out to work much better, sometimes Windows starts some background tasks which are also running on a specific core with high priority, and in that case if we force things to run on that same core it needs to wait until the Windows task has finished. You can still force it to run on a specific core though, see the new "Forced" checkboxes under CPU & Latency. Not recommended though!
1. Try run beta 039 and above on 1 core. If you watch Task manager You will see windows spreads it to few other cores. "Forced" does not help, it uses core0, then after few second core4, then 6 then 8, and i set it all to core 15. Beta038, and older betas, are fine. Sure i will not use 1 core, but it is easier to see what's happening.
2. When i use "dynamic speeds" on my 7 MB bands, cpu load rises from 44% to ~68%, on any beta/release. I just found "Start Attack Immidiately" Also uses much CPU.
Weird. "Forced" works fine here, I just verified it on the 9.40 release. If I select core 1 forced for multiple threads and increase the CPU load a lot, it all stays on core 1 and starts to buffer.
I also measured Dynamics on/off for both AGC and all MB1 bands, and it increased the CPU load from 51.5 to 52%, maybe (hard to see with such small numbers). So I don't know what's happening on your pc... Could be a cache issue - is this still an old Core2Duo or Core2Quad system?