What Is Hardware-Accelerated GPU Scheduling (HAGS)

What the toggle actually changes

Normally your CPU's graphics driver collects commands from games and apps, sorts them into batches, decides memory residency and pushes the work to the GPU. With HAGS on, a dedicated scheduling processor on the graphics card takes over the queue: the CPU submits work directly and gets back to the game, which trims per-frame submission overhead. The feature arrived with Windows 10 version 2004 and needs a WDDM 2.7-class driver — in practice NVIDIA GTX 10-series and newer, AMD RX 5000 and newer, Intel Xe and newer.

The toggle lives in Settings → System → Display → Graphics → Change default graphics settings, and Windows still ships it off by default on many machines. Turning it on asks for a restart, because it changes how the driver talks to the hardware — not a user preference. If the toggle is missing entirely, your driver or GPU does not support it, and that is the whole story.

The honest performance picture

Benchmarks across the board land in the same place: low single-digit percentages on average, mostly visible in CPU-bound scenarios at high frame rates, with an occasional latency improvement. If your game is GPU-bound — the usual case once settings are turned up — the scheduler is not your bottleneck, and the toggle changes nothing you can feel. Early driver years also brought stutter and capture conflicts on some setups, particularly with recording software, which is exactly why "try it and measure" beats folklore.

• Requires a WDDM 2.7+ driver: NVIDIA GTX 10-series / RTX, AMD RX 5000+, Intel Xe and newer
• Toggle: Settings → System → Display → Graphics → Change default graphics settings, then a reboot
• Helps most where the CPU is the limit: high-refresh displays, competitive titles, lowered settings
• Does nothing measurable when the GPU itself is already the bottleneck at your settings
• If capture or recording stutters after enabling it, the driver stack is the suspect — turn it off and compare

How to test it properly on your own machine

Cap your frame rate, pick one repeatable scene or a built-in benchmark, and record average plus 1% lows with the toggle off; then reboot, enable it, and repeat the same run. Compare your own numbers rather than a stranger's, because scheduler behavior depends on your CPU, your driver version and the specific game. If nothing changes, leave HAGS off and stop paying rent on the question; if you measure a real gain, keep it — and retest after every major driver update, because this is precisely the area drivers keep reworking.

Questions and Answers

Read next