• SONAR
  • Multithreading performance
2015/02/20 04:39:58
metz
Hey!
 
I've had some performance issues lately. Something I really havent had in ages since I have a hexacore Intel processor running 12 threads. But something I've noticed is that it's always thread no 1 that peaks and then makes the audioengine to stop. Multithreading is activated in the preferences. Any ideas? The load isn't at all evenly balanced over the threads.
 
Running Windows 8.1 Pro 64 bit, 24Gb RAM, Roland Quad Capture, several SSD-drives and Sonar Platinum. All latest drivers and firmware, bios etc from chipset to audio, graphics, storage etc... Sonar Platinum latest version.
 
/M
2015/02/20 07:11:23
scook
The imbalance is caused by one or more of the plug-ins in the project. Freeze or bounce and archive to reduce the load.
2015/02/20 07:31:33
emwhy
Scook is right, for example, the Abbey Road drums from Native instruments do this to my system all the time. You may also want to look into some under the hood tweaks like disabling core parking and if this is an Intel system, killing CPU EIST and disabling HPET in the BIOS. That helped my system at least cut down on core 1 doing all the work and made it run smoother.
 
2015/02/20 07:37:01
tenfoot
Have you disabled core parking?
2015/02/20 08:33:52
metz
Core parking? How do I do that?
 
Could be some synth or plugin I guess. I'll try freezing one at a time. Thanks for the tip. I use a lot of Arturia synths and well.... they've had problems before.
 
Thanks again!
 
/M
2015/02/20 09:08:00
gunboatdiplomacy
scook
The imbalance is caused by one or more of the plug-ins in the project. Freeze or bounce and archive to reduce the load.


what do you mean? do you mean the plug-in is not writen for multi threaded performance? i see the same issue with my 8-core Veshera PC. Once core is at 80, and the rest are at 20. running latmon, i found some issues and i've been able to cut down on drop-outs, but that core imbalance is still puzzling me.
2015/02/20 09:45:33
scook
It is a possibility.
2015/02/20 09:55:44
pwalpwal
this is probably not completely accurate, but i believe certain things always go through a single core, including the gui and the master buss, so one core is always busier than the others... after that the core distribution is roughly per-track (this is how live does it)... so you might try sub-bussing, or moving plugs from the master, see if that helps?
2015/02/20 10:06:29
gunboatdiplomacy
pwalpwal
this is probably not completely accurate, but i believe certain things always go through a single core, including the gui and the master buss, so one core is always busier than the others... after that the core distribution is roughly per-track (this is how live does it)... so you might try sub-bussing, or moving plugs from the master, see if that helps?


well, i have no plugs on the master. i was working last night on a song with one instance of kontakt, one instance of Ultra Analog and about 24 tracks of audio (with 6 busses) with varying amounts of Pro Channel use (ReMatrix/Tape/EQ/Comp/) and a couple instances of Wave's REDD Channel Strip. i'm getting better performance with regards to dropouts after updating my bios and turning off the energy savings setting there. but it still has the 80 to 20 split.
 
i also see the same core performance split in Reason, so it's not just Sonar. I wonder about AMD's version of Intel's Core Parking.
[heads off to google]
2015/02/20 10:13:36
jakelly
Take it from me Kontakt is a killer depending on what you're using. For core parking try this:
 
 
 
 
Trust me and those here who have mentioned it, disable core parking and you will see improvement. Also, if you can, as I stated above disable CPU EIST (also known as Speed Step) in the BIOS. These two tweaks will end a lot of grief for you.
 
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account