2.0 / LEGACY · 2.2.2.3Archived Legacy instructions; these controls do not describe 3.x Auto.Open the current guides ↗
← All guidesControls & modules / Memory, power & session extras

FIELD MANUAL / 09

Memory, power & session extras

Memory cleaning, cache warm-up and power-budget sharing solve different problems. Identify the bottleneck before enabling an option.

Reviewed against 2.2.2.3 / 2026-09-14
Where to find it
Advanced → Policies → Preset details / Session extras; power-plan toolbar
When it applies / restoration
Session settings restore from records on exit. Discarded cache data cannot be recovered through a settings reset.

Step by step

  1. First check for real memory pressure, disk contention or a GPU constrained by a shared power budget.
  2. Keep cleaning and warm-up at their defaults when memory is plentiful. Enable them only for a specific need and use the documented thresholds.
  3. Choose a suitable existing or managed power plan. Watch battery life and temperature on portable devices.
  4. After a session, inspect power/thermal limits and logs. Revert changes without a benefit.
Actual application screenshot, possibly from an earlier release. Follow the current text and interface for updated behavior. This module currently uses a Chinese screenshot; the instructions are fully translated.

Cleaning and warm-up do different jobs

Standby cleaning requires both list-size and genuinely free-memory thresholds; Task Manager’s Available value is not equivalent. Warm-up is off by default and reads at low priority after roughly 90 stable seconds on AC power with sufficient memory and an SSD, stopping on exit or memory pressure.

Power sharing requires evidence

On laptops with a power-limited GPU and CPU headroom, budget can be shifted toward the GPU. Observation, application and verification are separate stages. Missing evidence causes rollback; confirmed regression or no gain stops further attempts.

Handheld and session extras

Handheld disables CPU-idle blocking, idle policy, cache warm-up, VRAM residency and core exclusivity. DWM, audio latency and working-set trimming are separate options. Optional-service pausing only handles a fixed list and restores recorded changes on exit.

Page priority versus working-set trimming

Page-priority demotion changes reclamation preference without actively emptying memory. Working-set trimming actively removes eligible background pages from the working set. It is off by default and only attempted when available memory is below both 4 GiB and one eighth of total RAM, once per process instance, excluding anti-cheat.

Trimming can free physical memory, but returning to the app may require loading data again, causing page faults and slower initial response. More free memory alone does not prove a gaming benefit; compare long frames and app responsiveness too.

Reviewed sourcesrc/Ui/Pages/PanelForm.PolicyPage.cs ↗

Archived 2.2.2.3 instructions; source references are pinned to the public v2.2.2.3 tag.

Press Esc or click the backdrop to close