Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.botifymanager.xyz/llms.txt

Use this file to discover all available pages before exploring further.

The Process Optimizer is a suite of five subsystems that dramatically reduce the RAM and CPU cost of running many Roblox instances simultaneously. Together, they make it possible to run 15–30+ instances on hardware that would otherwise struggle with 5. Enable/disable everything with the master toggle: Settings → Memory & CPU Optimizer → Process Optimizer (Master).

​
Component Overview

Working Set Trimmer

Drops per-instance RAM from ~450MB to ~70MB by forcing Windows to page out idle memory.

CPU Affinity Manager

Pins each Roblox instance to specific CPU cores via round-robin assignment.

Process Priority Manager

Sets CPU scheduling and I/O priority to keep the OS and Botify responsive.

Crash Handler Killer

Auto-kills RobloxCrashHandler.exe every 30s — saves 15–30MB per instance.

Memory Monitor

Real-time per-instance and system RAM tracking with configurable warning alerts.

​
1. Working Set Trimmer

Forces Windows to page out Roblox’s idle memory to disk — dramatically reducing active RAM per instance.
ModeWin32 APIRAM per Instance
Gentle (default)SetProcessWorkingSetSizeEx~80–100 MB
AggressiveEmptyWorkingSet~60–80 MB
Deferred Mode (trim_only_in_game):
  • Waits ~2 minutes for bots to fully load before the first trim
  • Skips processes younger than 120 seconds to prevent connection timeouts during the join phase
Trim Interval: Runs every trim_interval seconds (default: 120s)
Enable Aggressive Trim when running 20+ instances. Pair with Ultra-Low GPU Mode for maximum RAM savings.
Real-World RAM Impact: 
No optimizer:     15 instances × 450 MB = 6.75 GB
Gentle trim:      15 instances × 90 MB  = 1.35 GB
Aggressive trim:  15 instances × 70 MB  = 1.05 GB

​
2. CPU Affinity Manager

Distributes Roblox instances across CPU cores using round-robin assignment — preventing multiple instances from competing for the same cores.
  • Core 0 is always reserved for the OS and Botify
  • Each instance is pinned to cores_per_instance cores (1–4, configurable)
  • Assignments are re-verified on each optimizer cycle in case processes respawn
Example — 8-core CPU, 2 cores per instance: 
Instance 1 → Cores 1–2
Instance 2 → Cores 3–4
Instance 3 → Cores 5–6
Instance 4 → Cores 7–8
Instance 5 → Cores 1–2  (wraps)

​
3. Process Priority Manager

Sets both CPU scheduling priority and I/O priority for all Roblox processes.
PriorityRecommended For
Realtime⚠️ Not recommended — can destabilize the system
High1–5 instances
AboveNormalLight loads
NormalWindows default
BelowNormal10–20 instances (default)
Idle20+ instances
Also sets I/O priority to Very Low via NtSetInformationProcess — prevents disk-heavy Roblox asset loading from blocking other processes.

​
4. Crash Handler Killer

RobloxCrashHandler.exe launches automatically with every Roblox instance and serves no purpose for bot accounts.
  • Auto-killed every 30 seconds
  • 15–30 MB saved per instance
  • At 20 instances: saves 300–600 MB total
  • Safe to kill — does not affect gameplay, stability, or connectivity

​
5. Memory Monitor

Tracks system and per-instance memory in real time (updates every 10 seconds):
MetricDescription
Total Roblox RAMSum of all Roblox process working sets
Per-Instance AverageTotal Roblox RAM ÷ running instance count
System RAM %OS-level memory utilization
Available RAMFree system memory
Est. Max Additional Instances(available RAM − 1 GB) ÷ 100 MB
Warning appears in the status bar when system RAM exceeds memory_warn_threshold (default: 85%).
Instance CountWorking SetAggressiveGPU ModePriorityMax Concurrent
1–5OptionalOffLow GPUNormal5
6–14OnOffLow GPUBelowNormal14
15–25OnOnUltra-LowBelowNormal25
25+OnOnUltra-LowIdle40+