Yes, the Multi-threading preference is measured as a "percentage of available cores". If you have an 8-core system and select 25%, KS will use 8 * 0.25 = 2 threads, (which the OS/host should schedule on two separate cores). 50% would be 4 threads in this case. etc.Wanterkeelt wrote:Andrew, the new beta works flawlessly on my i7 3930K, Win7, Reaper 5.2 so far. Great job !
You mentioned somewhere that you recommend to set buffer size to AUTO, but what about Multithreading ? Does Multithread 25% mean it will use 25% of the number of cores of the CPU ? I simply went 100% and it seems to distribute the calculations on all cores +- equally. Right ?
100% is usually a good choice for normal use, as it will avoid putting too much stress on a single core. But, there is some degree of overhead to split things into threads and then recombine them. So in some cases "threading more than you need to" is not completely ideal. For example if you are using a ton of KS instances in a DAW all at the same time, you can get a few more instances by using 25% or 50% and keeping most of the processing of each instance on a few number of cores since the host will spread the load of all the KS instances over the available cores. i.e. there is less sense to heavily thread single instances when the host itself will thread the collection of multiple instances...
If you are bouncing/freezing a single KS track within a project, you should keep OFFLINE set to 100% since during the export the only thing that is happening is the single-instance KS processing so you want KS to use as much of your CPU resources as possible so that render time is a fast as possible...
Keeping everything set to 100% is good bet, and if you like you can experiment with 25 or 50% for realtime depending on how complex your host project is and what else is going on in it. When in doubt, just keep everything at 100%.
Keeping things at 100% may also help prevent error messages in Logic when changing some parameters...