Windows: CPU Core Un-Parking

My choice is the Quick CPU tool

It turns out there are quite a few tools for adjusting CPU optimization. I chose, in my opinion, the best one.

Quick CPU is without a doubt the best, with all the options I might need. Sadly, it’s not available on scoop or winget. Now it is on scoop install quickcpu thanks to my request

ThrottleStop is probably the most well-known

Process Lasso and ParkControl by Bitsum

Intel XTU is the official tool

ThrottleStop

ThrottleStop is probably the first application that dealt with these optimizations. I like that it’s available on scoop, but I don’t like that it’s too complicated to set up. Also, it’s not exactly easy to quickly set ThrottleStop to start automatically when the computer is turned on.

Since I also used ThrottleStop for a while, I wrote down for myself how to add it to automatically start with all admin privileges. There are two ways to do this, manually and semi-automatically.

Manual Setup

Create a Scheduled Task to trigger at log on.

In the Create Task dialog, select the following:

• General (tab), Run with highest privileges
• Triggers (tab), New (button), Begin the task, At log on

Copy-paste commands in the terminal

First, adjust the value to the correct path where the application is located, then in Powershell type:

$App = """$(scoop prefix throttlestop)\ThrottleStop.exe"""
$Name = "ThrottleStop Autorun"

$Action = New-ScheduledTaskAction -Execute "$App"
$Trigger = New-ScheduledTaskTrigger -AtLogon
$Principal = New-ScheduledTaskPrincipal -UserID "$env:USERDOMAIN\$env:USERNAME" -LogonType ServiceAccount -RunLevel Highest
$Settings = New-ScheduledTaskSettingsSet -AllowStartIfOnBatteries -DontStopIfGoingOnBatteries -DontStopOnIdleEnd
$Task = New-ScheduledTask -Action $Action -Trigger $Trigger -Settings $Settings -Principal $Principal
Register-ScheduledTask -TaskName "$Name" -InputObject $Task -Force

Overall, Quick CPU is the best tool for CPU Core Un-Parking, while ThrottleStop is an alternative that is widely used, but it’s complicated to set up and not easy to start automatically.

Naknadno sam počeo da se premišljam

Nakon malo duže upotrebe, počeo sam opet da testiram ThrottleStop umesto QuickCPU iz dva razloga:

1. Zazeće memorije i veličina programa su neuporedivi. Dok ThrottleStop zauzima 1.5M, QuickCPU je na čak 150M
2. ThrottleStop poseduje “Windows Defender Boost” opciju koju QuickCPU ne poseduje

Druga stavka je detaljano objašnjena u ovom članku Windows Defender can significantly impact Intel CPU Performance i u ovom Windows Defender is using more system resources on Intel PCs a napravljen je i odvojeni tool baš samo za ovu namenu po dimenom Counter Control takođe od TechPowerUp.

C:\Users\Common User\scoop\apps\throttlestop\current