However, we find that Windows is often over-aggressive in its core parking, resulting in excess latency as cores are unparked to accommodate bursting loads (the most common type of CPU load). There are many factors that will determine how efficacious it will be for any given system, including the CPU type, application load, and user behavior. And that is exactly the desired tweak for most users: disable parking only for high performance power plans.Įmpirical evidence shows that disabling core parking can make a real difference in system performance. That means you can, for example, disable core parking for the High Performance power plan, but leave it enabled for other plans. The core parking settings in Windows are implemented as parameters of power plans (aka power profiles). A number of complex parameters control when a core should be parked, and Microsoft tuned heavily towards power savings. Their interest was in conserving energy, even if this meant marginally decreasing performance. The problem is that Window's default power profiles are configured far too aggressively when it comes to core parking, especially on workstations. This technology is very similar to frequency scaling, in that it seeks to throttle the CPU when idle. Disabled cores are re-enabled as the CPU load increases once again. Core Parking dynamically disables CPU cores in an effort to conserve power when idle. Bitsum ParkControl Pro 1.3.1.8 Multilingual | 2.6 Mbīitsum developed ParkControl because core parking settings are hidden in Windows, but can make such a large difference on performance, particularly when there are bursting CPU bound loads (the most common type).Ĭore Parking is a sleep state (C6) supported by most newer x86 processors, and newer editions of Windows.
0 kommentar(er)
