Once the utilization level rises above a certain threshold (where utilization is the fraction of time spent running processes other than the idle process) or the mean time spent in the ready queue exceeds a certain value it would make sense to wake a core up. In fact, it may be faster to simply wait in the queue and run on a logical processor that's already unparked rather than wait for one that is parked to be awoken. I'm not certain what mathematical model Windows uses by default to determine when to unpark cores, but it's most likely some sort of moving average of utilization or queuing delay. This causes the thread/process to wait longer in the queue than it would normally, but avoids waking the core.

Alternatively it can keep the cores parked and simply throw the thread/process onto the ready queue. However, this causes the microprocessor to consume more power. If one or more cores are parked it can wake them up and load the thread/process onto the logical processor representing that core. When threads (and/or processes depending on the operating system's model) become ready for execution the operating system has a decision to make. Parking is something that an operating system can do to put a core to sleep when there's not enough work to do to justify keeping it powered up.

I've discovered some pretty simple ways of increasing overall FPS and smoothness in Dark souls 3 so i thought i would share them.Ĭores are unparked by default.

Quick cpu vs unpark