- Frame rate, 1 % low and hitches come from msBetweenDisplayChange of the
frames that reached the screen; frames never shown are counted apart and
the presented rate is kept as presented_fps. A game presenting 60 fps
while the screen changes every 167 ms now shows as the stutter it is.
- A window whose capture failed, a busy window where the LLM finished no
answer, and every busy window when the STT load failed are not counted.
- A yielding window counts only when every Jarvis process got both its
CPU and its GPU priority lowered.
- The "game hardly drawing" floor applies only with Jarvis off or idle, so
a game Jarvis slows that far still counts as harm.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The 95 % GPU cap is gone: it did not lower utilisation, slowed the LLM and
a YouTube video did not stutter without it. What it was meant to protect
is now measured directly in a game. The new on-demand game_frames stage
records the game's frame times with PresentMon (pinned by hash, game
process only, CSV deleted after reading) with Jarvis off, idle and busy in
the game placement, and busy while Jarvis yields: its processes at
below-normal CPU and GPU scheduling priority, read back to confirm, then
restored. Busy rows run A B B A. The design docs record the candidate and
the pre-registered rule for adopting it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>