Skip to content

Saiyan Mode

Jump to bottom
gokuthug1 edited this page Oct 5, 2026 · 1 revision

Saiyan Mode

Saiyan Mode adjusts how Windows schedules your Roblox Player processes. It does not modify Roblox, inject anything, or change network behaviour.

Off by default. Nothing happens until you enable it and press Save & apply policy.

What it does

Two independent controls:

Control Effect
Roblox process priority Above Normal or High, instead of Windows' default
Advanced CPU affinity mask Restricts the process to specific logical CPUs

Plus an optional preference for faster CPU cores where Windows can tell us which ones they are.

Safety model

  • Only processes that are both verified as Roblox Player and verified to be running from an installed location are managed. A non-Player process is rejected outright.
  • Windows default is a true no-op. Selecting it performs no priority or affinity write at all, and resets to the original policy.
  • Priority-only management never touches affinity, including on multi-group systems.
  • On restore, only the fields that were actually changed are written back.
  • Every change is recorded in a restore journal keyed by process. If a process exits, its journal entry is pruned.
  • No elevation is requested. If Windows denies the action, GokuTrap reports "Windows denied or could not perform the action" and Roblox carries on.

Priority options

Option Risk
Windows defaults (preserve original) None. Recommended
Above Normal (conservative) Low. Usually unnoticeable to other applications
High (advanced) See the warning below

Warning High priority may make audio, the desktop and other applications less responsive while Roblox is running. Apply it only if you understand the effect, and revert to Above Normal if anything else on the machine starts behaving badly.

CPU affinity

An optional hexadecimal mask. Bit 0 is logical CPU 0, bit 1 is CPU 1, and so on. For example, 3 selects CPUs 0 and 1.

  • Leave the field blank for Windows default scheduling.
  • A value of 0 is invalid — it means no CPU at all.
  • The mask may contain only detected, available CPUs. Anything else is rejected with a specific message rather than silently clamped.
  • Affinity is only offered when the machine has a single processor group and every logical processor fits in a 64-bit mask. On multi-group systems the option is disabled, because a 64-bit mask cannot express the whole machine.

Prefer faster efficiency classes

Where Windows reports distinct CPU efficiency classes, GokuTrap can prefer the higher ones. A higher efficiency-class value means a faster, less power-efficient processor.

  • The option is only offered when distinct classes actually exist. On a uniform CPU it stays unavailable and the UI says so.
  • This is not an AMD 3D V-Cache / CCD inference. GokuTrap has no reliable way to detect cache topology, so it does not guess.

The topology summary reports what Windows actually said, for example:

Windows CPU topology: 8 logical CPUs, 4 cores, 1 groups. OS topology available; no distinct efficiency classes. Automatic performance-core selection unavailable.

Memory diagnostics

Two manual, explicit buttons. Neither runs automatically.

Measure memory

Samples each verified Player process:

PID 1234: working set 512 MiB / private bytes 640 MiB

  • Working set is resident RAM — pages currently in physical memory.
  • Private bytes is committed private memory.

Neither figure is a frame-rate measure. GokuTrap does not display FPS here because it has no non-invasive source for it — see Platform-Limits.

Trim selected working set

Calls Windows EmptyWorkingSet on one selected Player process, after you confirm.

Warning This removes resident pages from the process's working set. Pages may immediately come back, and paging may cause stutter. Trimming is not heap compaction and not garbage collection, and no performance improvement is implied. It is a one-time manual action, never a background cleaner loop.

If GokuTrap cannot restore a policy on a still-running process, it says restoration was denied and that it will retry — restart Roblox to recover the original scheduling.

Reverting

Press Reset to Windows defaults. This disables management and restores the captured original policy for every verified process. See Feature-Tools-Overview#On shutdown for forced-termination behaviour.

What this cannot do

  • It cannot make Roblox run faster in a measurable, guaranteed way. Scheduling priority changes how aggressively the CPU is shared, not how much work Roblox does.
  • It cannot compact a managed heap, free GPU memory, or stop Roblox from allocating.
  • It cannot select between CPU generations beyond what Windows reports as efficiency classes.

Clone this wiki locally