GuideTweak tabs

Advanced tweaks

Memory management and how Windows splits CPU time between foreground and background work.

Memory and process-scheduling tweaks covering memory compression, page combining, SysMain, and how Windows splits CPU time between foreground and background work.

Memory

  • Disable Memory Compression turns off in-RAM memory compression. Lowers CPU overhead at the cost of slightly higher physical memory use.
  • Disable Page Combining turns off the kernel feature that deduplicates identical memory pages, reducing CPU overhead at rest.
  • Disable SysMain (SuperFetch) stops the SysMain service. Recommended only if the system is SSD-only; if an HDD is present you may keep it enabled unless it's causing high disk or CPU usage.

Scheduling

  • Process Scheduling controls Win32PrioritySeparation, which decides how Windows shares CPU time between programs. Windows runs each thread for a brief slice of time (a “quantum”) before switching to the next, and this setting tunes three things about those slices:
    • Length. Short switches between threads quickly for a snappy desktop and lower input latency in games, while Long runs each thread longer for raw throughput (the server default).
    • Type. Variable gives whatever app is in the foreground a longer slice, while Fixed gives every app the same slice regardless of focus.
    • Foreground boost. How much more CPU the app you're actively using gets over background work (1:1 is none, 3:1 is triple).
    Each option in the app is labelled with this decode plus the raw value. Recommended: Short · Variable · 3:1 (38), which matches the client default. Windows’ own default (2) resolves to exactly this on desktop editions, so picking 38 just makes it explicit and immune to edition differences (on Server, 2 resolves to Long · Fixed · 3:1 instead).

    Windows 11 24H2 / 25H2 note: on 24H2 and later the kernel sizes Variable (dynamic) slices from each process’s Quality-of-Service level, meaning foreground versus visible versus background, rather than from the Length and ratio bits (25H2 shares 24H2’s kernel, so it behaves identically). So on these builds the Variable options (including the recommended 38) all behave like the default. The Fixed options take a different path that isn’t QoS-driven, giving every app the same slice regardless of focus, though 24H2 also shrank the underlying quantum unit roughly six-fold, so the exact slice lengths differ from older builds either way. It’s safe to set on any Windows version; we keep 38 as the default-matching recommendation.