Does setting a game to High priority make it faster? We measured.
It's one of the oldest PC gaming tips: open Task Manager, find the game, right-click, Set priority → High. Free frames.
We tested it the boring way: the same fixed piece of work, run three times as it is and three times at a higher priority, taking turns, on the same PC. Then we did it again with something else running.
Alone: nothing
Our test PC is a Ryzen 7 7800X3D. The work is a fixed job on one core, the kind of work a game's main thread does. Nothing else heavy was running:
| run 1 | run 2 | run 3 | |
|---|---|---|---|
| As it is | 14.4 s | 14.3 s | 14.3 s |
| Above normal priority | 14.3 s | 14.3 s | 14.2 s |
No difference. The gap is smaller than the gap between two ordinary runs.
That's not a fluke. Priority doesn't make a CPU faster. It only decides who goes first when two programs want the same core at the same time. With nobody else waiting, there's no line to jump.
With competition: 12% faster
Then we started a second job in the background that kept every core busy at normal priority, about 15 cores' worth of work on a 16-thread CPU. Same test:
| run 1 | run 2 | run 3 | |
|---|---|---|---|
| As it is | 16.1 s | 16.4 s | 17.3 s |
| Above normal priority | 14.3 s | 14.3 s | 14.3 s |
As it is, the work slowed down and wobbled, because it had to share. At above normal priority it went straight back to 14.3 seconds, exactly its time alone. That's 12% faster than the best ordinary run.
And it was no faster than alone. Priority didn't add speed. It took back the speed the other job had been taking. That time came from the other job, which had to wait instead.
So when does it help a game?
Only when something else is fighting the game for the CPU while you play:
- Streaming or recording on the CPU (an x264 encoder in OBS, for example). But raise the game, and the encoder is what waits, so watch for a stuttering stream.
- A download that's unpacking, a game update installing, a big file sync.
- An antivirus scan or Windows Update kicking in mid-game.
- A second program you left working: a render, an export, a compile.
If your PC is just running the game, priority has nothing to win. Close the competition first. That helps more, and nothing has to wait.
Honest note: our test work is game-shaped, not a game, and we tested Above normal, one step below High. Real games use several cores, so the same rule should hold per core: priority only matters when cores are full. We didn't test High. Windows warns that changing priority can make the system unstable. We'd never use Realtime: it can take the CPU away from your mouse, keyboard and sound.
How to check yours
- Play the way you normally do, and open Task Manager → Performance → CPU while you do.
- If the CPU isn't near 100%, there's nothing to win: leave priority alone.
- If it is, look under Processes for what besides the game is using the CPU, and close it if you can.
- If it has to keep running (your stream, say), try Details → right-click the game → Set priority → Above normal. It resets when the game closes.
Or let Headroom measure it: its tune test runs the same work three times as it is and three times at above normal, taking turns, and only calls it a gain if it beats the normal run-to-run wobble. Here, alone, it said "no measurable gain". With the competition running, it said "12% faster". Both were right.
Headroom measures this on your own PC, free, and nothing leaves your computer.
Get Headroom