FIELD MANUAL / 08
Policies & background suppression
Policies cover game priority, background scope and session extras. The current source uses Core control, Preset details and Session extras; core selection has moved to its own page.
- Where to find it
- Advanced → Policies
- When it applies / restoration
- Primarily applied during game sessions. Some presets control or restrict individual switches.
Step by step
- Check the effective mode. Mode-controlled options may be locked or labeled rather than independently editable.
- Review background suppression, background GPU priority and game-process priority under Core control.
- Preset details covers scope, recording and multimedia policies; Session extras includes service, memory and input options.
- Change one option at a time, compare a new session and verify actual writes in the log.
What suppression changes
Eligible background processes can receive lower CPU, disk-I/O and paging priority, EcoQoS and timer-resolution limits. GPU demotion is separate. Windows dynamic priority boosting is distinct from CPU turbo frequency.
Protection boundaries remain
Esports mode does not remove general exemptions for core Windows services, anti-cheat, input/audio, peripherals, hardware tools or other signed-in users. Whitelist scope adds further exemptions.
Candidate threads are not proven frame-critical threads
Thread candidates are inferred from observations such as CPU time and may be wrong. Availability depends on hardware and mode. If performance regresses, disable the option for that game and repeat the same-scene comparison.
How CPU and disk work yield
Eligible ordinary background work receives Idle process priority and Very Low disk-I/O priority directly. It yields under contention but can keep working with spare capacity, so nonzero background CPU is expected. Suppression does not enforce a fixed CPU percentage cap.
EcoQoS, timers and priority boosting
EcoQoS asks the OS to favor energy-efficient background execution. Where supported, the process’s high-resolution timer requests are also ignored. These affect execution treatment and wake precision, rather than imposing hard E-core pinning or disabling turbo.
Pudding retains Windows dynamic priority boosting so background work that the game depends on can finish promptly. Starving all background work can otherwise lengthen game waits.
What GPU yielding covers
Background GPU demotion is separate and only lowers eligible process scheduling priority. The source skips this write while HAGS is active. It does not empty VRAM, disable animation or move a running app to the integrated GPU.
Archived 2.2.2.3 instructions; source references are pinned to the public v2.2.2.3 tag.