FIELD MANUAL / 01
How it works: making room for the game
Background suppression is central to Pudding: eligible background work yields when the game needs resources. Follow a session to understand what each control changes, which processes it affects and how restoration works.
GAME ON. SETTINGS BACK.
Automatic takeover.
Automatic restoration.
When the game ends, session settings automatically return to their recorded pre-game values. Background suppression, game priority and core affinity restore without manually resetting each control.
- 01Record originals
Save the state before changes
- 02Prioritize play
Apply your session settings
- 03Restore on exit
Automatically restore records
Failed restoration retains records for another attempt at startup. System-environment settings, application GPU preferences and per-EXE compatibility settings restore separately. Cache cleaning, file deletion and one-time input-language changes are outside automatic restoration.
Restoration scope & troubleshooting ↗- Where to find it
- Read this overview, then configure the relevant controls in Policies, Core scheduling and Whitelist.
- When it applies / restoration
- Session policies apply after protection recognizes a game. Game exit or disabling protection triggers recorded restoration.
The scheduling flow of a session
- Recognize the game: identify its executable and load its profile, inheriting global values where no override exists.
- Establish exemptions: protect the game, whitelist and essential system paths, then select background targets using the mode and family settings.
- Apply resource yielding: eligible ordinary background processes receive Isolated suppression immediately. Game priority and other extras follow their own controls.
- Reconcile and restore: handle new processes and verify writes during play. Restore original values on exit and retain failed recovery records for later retries.
Why less contention can make a game steadier
Producing a frame involves CPU work, resource reads and GPU submissions. Background extraction, sync, web animation or updates can compete for those resources and delay some frames. Pudding changes how competing work is scheduled to reduce waiting and long frames.
Contention-heavy workloads offer more room for improvement. A clean system or a game limited by raw GPU rendering capacity leaves less to recover. The suppressed-process count measures targets handled, not an FPS gain.
What suppression actually changes
This table describes eligible ordinary background processes. CPU, disk I/O, memory-page priority, EcoQoS and timers form baseline suppression; GPU demotion and working-set trimming have separate switches.
| Resource | Action | Practical effect |
|---|---|---|
| CPU time | Lower the process priority class to Idle while retaining Windows dynamic priority boosting. | Background work yields under contention and can still run with spare capacity. There is no fixed CPU percentage cap. |
| Disk I/O | Set background I/O priority to Very Low. | Background reads and writes yield under contention, subject to the storage stack and workload. This does not cap download bandwidth. |
| Memory pages | Lower memory-page priority. | Background pages are easier to reclaim under memory pressure. This step does not actively empty process memory. |
| Energy-aware scheduling | Enable EcoQoS for background work through the OS. | The OS can favor efficient frequency or core choices. This is neither hard E-core pinning nor a global turbo-off switch. |
| Timers | Ignore high-resolution timer requests from that background process where supported. | Background timers lose the guarantee of the requested high resolution. This does not lock the game to a fixed timer value. |
| GPU (optional) | Optionally lower background GPU scheduling priority; skip this write while HAGS is active. | Reduce contention where supported. A running application is not moved to a different GPU. |
| Working set (optional) | When enabled, trim once per process instance only if available memory is below both 4 GiB and one eighth of total RAM. | Free physical memory, at the cost of possible page faults and slower return to the app. Anti-cheat is excluded. |
Smart, Esports and Handheld: which processes yield
Once an ordinary background process passes the protection boundary, the current version applies Isolated suppression directly, without a heat threshold or gradual escalation. Smart exempts the application family you are using; Esports expands the scope and can keep an app suppressed after you alt-tab to it.
Handheld shares the Esports background scope but differs in power behavior and available extras. Custom exposes individual choices. Smart adaptive escalation is separate and off by default; enabling it permits temporary scope expansion during sustained CPU saturation.
Which processes are exempt
General suppression skips protected game processes, whitelist entries, core Windows services, anti-cheat, game network accelerators, input/audio paths, peripheral and hardware tools, and other signed-in users. Esports retains these exemptions.
Game families are exempt by default: platforms, launchers, resident game-directory processes and descendants. Per-game family suppression makes eligible related processes candidates for ordinary suppression; the game, whitelist and other protections remain.
Game priority and core exclusivity solve different problems
Game-process priority raises CPU, disk-I/O, page and GPU scheduling treatment for the target renderer, while suppression lowers the treatment of competitors. Candidate-thread priority additionally favors threads inferred from clues such as CPU time; these are not proven frame-critical threads.
Core selection limits where the game can run. Exclusivity steers eligible ordinary background work away from selected physical cores. Baseline suppression does not hard-pin all background work to E-cores or the last core. Hard locking outside the exclusive range is a separate, default-off option; system interrupts may still use game cores.
An alt-tab example
Suppose a browser is doing background work while you play, and it is neither whitelisted nor part of the game family. Smart suppresses eligible background work, then exempts the browser and its protected family when you switch to it. Esports can keep it suppressed, making it feel slower after alt-tab.
Whitelist the specific executable and necessary children if it must stay responsive while gaming. For platform chat or overlay problems, first check the game’s family-suppression setting.
What Isolated means, and how changes restore
Isolated is a resource-scheduling level: ordinary background work keeps running with lower treatment under contention. General suppression neither suspends processes nor applies a hard Job CPU cap. Optional service pausing and launcher detachment have their own actions and controls.
Original priority, affinity, I/O, page, QoS and related states are recorded before mutation, then writes are checked. Exit or disabling protection attempts restoration; the next launch retries remaining records after an abnormal exit. Persistent system options, GPU preferences and file cleanup follow their own module rules.
Archived 2.2.2.3 instructions; source references are pinned to the public v2.2.2.3 tag.