So, I don't know where to post this, but I thought it would be relevant to all streamers and the OBS community is growing so I thought I'd throw this in here.
I learned about disabling core parking earlier today as a way to reduce microstuttering and after doing it, it has increased my system responsiveness by I would say 400%. I have a i5-3570k and I've also tried this on my laptop, which is a older Core2 T8300. This affects anything with more then two cores, which is pretty much all modern processors. I'm unsure of how Windows 8 deals with this and/or if it would show benefits on W8, but in Windows 7 it makes a huge difference.
Core parking is a feature that saves power by turning off cores with low workloads... This can happen for a few micro-seconds and may even happen when the core is under load. For instance my main computer never showed up as 'parked' in resource monitor, but after doing this I noticed a huge improvement in responsiveness and system latency. It's the easiest to feel with my mouse and when typing. Basically both inputs showed huge improvements in resposivness.
It also has quantifiable results in some applications. Basically anything that is sensitive to latency, such as encoding, gaming, and audio work shows improvements.
I personally haven't tried gaming or streaming yet, so take this with a grain of salt. It also has a downside as it increases power usage. I personally have not seen a increase in power usage while monitoring with Argus Monitor and all my C-States still work (CPU clocks down and uses less power when not under load). The benefits are tremendous though.
If you use a AMD Bulldozer or Vishera, this improves system responsivness and performance!
http://bitsum.com/about_cpu_core_parking.php (It's called Parkcontrol partway down the page)
Most of the fixes use registry keys, but that's an actual program to disable it. It also allows you to modify the setting for battery profile as well (in case you use a laptop and aren't plugged in). I personally have not seen a downside to it yet (fingers crossed) and of course, use at your own risk. If your system catches fire I had nothing to do with it.
Let me know what sort of results you guys get. You don't need to reboot after using it either.
I learned about disabling core parking earlier today as a way to reduce microstuttering and after doing it, it has increased my system responsiveness by I would say 400%. I have a i5-3570k and I've also tried this on my laptop, which is a older Core2 T8300. This affects anything with more then two cores, which is pretty much all modern processors. I'm unsure of how Windows 8 deals with this and/or if it would show benefits on W8, but in Windows 7 it makes a huge difference.
Core parking is a feature that saves power by turning off cores with low workloads... This can happen for a few micro-seconds and may even happen when the core is under load. For instance my main computer never showed up as 'parked' in resource monitor, but after doing this I noticed a huge improvement in responsiveness and system latency. It's the easiest to feel with my mouse and when typing. Basically both inputs showed huge improvements in resposivness.
It also has quantifiable results in some applications. Basically anything that is sensitive to latency, such as encoding, gaming, and audio work shows improvements.
I personally haven't tried gaming or streaming yet, so take this with a grain of salt. It also has a downside as it increases power usage. I personally have not seen a increase in power usage while monitoring with Argus Monitor and all my C-States still work (CPU clocks down and uses less power when not under load). The benefits are tremendous though.
If you use a AMD Bulldozer or Vishera, this improves system responsivness and performance!
http://bitsum.com/about_cpu_core_parking.php (It's called Parkcontrol partway down the page)
Most of the fixes use registry keys, but that's an actual program to disable it. It also allows you to modify the setting for battery profile as well (in case you use a laptop and aren't plugged in). I personally have not seen a downside to it yet (fingers crossed) and of course, use at your own risk. If your system catches fire I had nothing to do with it.
Let me know what sort of results you guys get. You don't need to reboot after using it either.
