Install & calibrate
Acquire the EXE, confirm ProBalance is armed, and let defaults run through a real workload day before customizing.
Open walkthrough →walkthroughs
Operator walkthroughs
Short routes from install to durable CPU control — without drowning in every checkbox. Follow the paths below for first-run calibration, ProBalance tuning, affinity discipline, Watchdog automation, and Governor deployment.
v18.2.2.10
5 walkthroughs
Windows 7–11
Bitsum
Baseline window
24h
Observe before writing rules
Rule depth
3 tiers
Default → profile → hard pin
Workloads
Gaming · Dev · SRV
Scenario walkthroughs below
Service mode
24/7
Governor keeps policies alive
Tune input smoothness
Learn when ProBalance should nudge priorities versus when a persistent rule is the cleaner fix.
Open walkthrough →Pin & isolate cores
Keep latency-sensitive apps on clean logical processors and push noisy helpers to the edges.
Open walkthrough →Automate guardrails
Watchdog caps runaway builds, memory hogs, and stuck helpers — Governor makes it survive logoff.
Open walkthrough →First-run calibration
Process Lasso is most effective when you understand your machine’s baseline before stacking rules. Treat day one as telemetry, not surgery.
1
Install
Run the 2.72 MB EXE with admin rights. Keep defaults.
2
Verify
Confirm ProBalance and Governor show active in the tray menu.
3
Observe
Use your normal apps — games, IDE, browser tabs — for 24 hours.
4
Rule
Promote repeat offenders to named rules only after patterns emerge.
- Download from the official bay. fetch build 18.2.2.10 from download.html and verify the package size (~2.72 MB) before running elevated setup.
- Leave ProBalance enabled. It is the default input smoothness guard. Disabling it on day one removes the signal you need to judge whether custom rules are necessary.
- Skim the process list once per session. Note which processes spike CPU during your heaviest tasks — compilers, game launchers, backup agents, browser GPU helpers.
- Defer affinity pins. Until you know which cores stay cool under load, pinning can accidentally trap latency on busy logical processors.
- Export a blank config snapshot. After week one, save your .ini so future experiments have a rollback point.
Signals worth a custom rule
- Same executable pegs CPU every launch despite ProBalance
- 在竞技比赛期间运行背景索引器
- 远程桌面助手饿死前景输入
- 备份作业与夜间编译批处理作业重叠
暂时忽略的信号
- 一次性更新
- 短引导后索引器通过
- 您自行安排的防病毒扫描
- 游戏启动器在空闲状态下进行补丁更新
ProBalance调谐
ProBalance动态抑制CPU猪，因此前台工作可以保持键盘和鼠标延迟不变。它不是亲和力规则的替代品，而是第一响应者。
当ProBalance足够时
- 在办公室或浏览会话期间偶尔出现背景峰值
- 游戏期间的单个流氓选项卡或助手流程
- 使用电池的笔记本电脑，需要轻微的节流，而不是硬盖
何时添加永久性规则
- 每⟧次发射⟧后⟦T1持续反复战斗⟦T0
- 您需要保证音频/输入管道的优先级
- 无论前台状态如何，服务器角色都需要固定类
实用调音梯
- 默认侵略性 —保持一周不变。在简单日志中记录口吃事件（时间、应用程序、CPU% ）。
- 每道工序约束 —在硬性优先级更改之前，右键单击重复违规者→“ProBalance约束”。
- 前景提升对 —仅当⟦T0无法保持帧时间稳定时，才能提⟧升您的游戏或DAW职业。
- 按标题禁用 —具有反作弊敏感性的罕见竞争性标题可能需要排除；在配置说明中记录原因。
亲和力纪律
CPU亲和力将进程固定到逻辑处理器集。使用得当，它们可以隔离延迟；使用得早，它们可以将工作负载困在错误的内核上。
核心选择启发式
- 为游戏、音频和输入密集型应用程序保留时钟频率最高的内核
- 将Windows服务+更新程序推送到大型⟦T1上的最后2–4⟧个逻辑处理器
- 尽可能将虚拟机监控程序/WSL2池与游戏集分开
- 在混合⟦T0上，首选⟧P核以获得延迟； E核用于渲染批处理
常见错误
- 将所有内容固定到CPU 0 —最古老的核心很少是最干净的
- 一对匹配游戏+ Discord +浏览器—峰值堆栈
- 在不检查核心计数的情况下从论坛复制随机.ini相似性
- 硬件升级后忘记清除相似性
Watchdog食谱
当进程超过CPU、内存或实例阈值时，Watchdog规则会自动响应--非常适合编译场、改装游戏和无人值守的助手。
Runaway compiler
If cl.exe or rustc holds >90% CPU for 90s while idle desktop, reduce priority and log the event.
Memory hog
Cap helper suites that leak over sessions — restart when working set crosses a defined GB threshold during overnight jobs.
Stuck launcher
Auto-restart game platform processes that hang at 0% CPU with a frozen window for more than 3 minutes.
Watchdog checklist
- Define the trigger metric (CPU %, memory, instance count, runtime)
- Choose a proportional action before a nuclear one — throttle, then terminate
- Log actions when running on shared workstations for audit trails
- Test rules during low-stakes hours; document false positives
Governor on servers & GUI-less rigs
Process Governor is the Windows service that keeps Process Lasso policies alive after you close the GUI — essential for servers, render nodes, and kiosk PCs.
- Install with service option enabled during setup or via Options → “Start Governor at boot”.
- Confirm service recovery in services.msc — set restart on failure for unattended racks.
- Apply policies from a template machine then export/import .ini for fleet rollout.
- Restrict who can edit rules on shared hosts; pair with the Safety & integrity deployment checklist.
Server profile
- Persistent priority for database / queue workers
- Affinity maps that keep noisy agents off socket 0
- Watchdog on runaway maintenance scripts
Workstation profile
- ProBalance for daily desktop input smoothness
- Per-game affinity only after baseline week
- compact Watchdog on mod tools and dev servers
Workload scenarios
Pick the lane closest to your machine — each path stacks the earlier walkthroughs in a sensible order.
Frametime first
- Day 1: ProBalance only + baseline logging
- Day 3: Affinity for game + audio; push launchers outward
- Day 7: Watchdog on known leaky overlay tools
Compile + IDE harmony
- Keep ProBalance for browser + indexer noise
- Affinity: IDE on P-cores, batch compiles on E-cores / tail set
- Watchdog on runaway test runners
Policy durability
- Governor at boot with recovery enabled
- Persistent rules for service roles
- Change control on imported .ini files
When rules fight each other
Symptoms like micro-stutter, uneven frametime, or “stuck” priorities usually mean overlapping policies — not a broken engine.
Diagnostic order
- Temporarily disable newest Watchdog entries
- Clear affinities on suspects; retest 15 minutes
- Lower manual priority boosts — let ProBalance breathe
- Re-import last known-good .ini snapshot
Still stuck?
Check the 常见问题 for antivirus exclusions, Governor permissions, and licensing boundaries. Integrity verification steps live on Safety & integrity.