On the game PC the game went behind another window right after Jarvis started and stayed there for three windows, drawing at its background rate (about 58 fps). The kit only checked the window in front at the end of a window, so the window in which the user clicked back into the game counted and showed yielding as a 47 % drop in 1 % low. - FrontWatch checks every second from the start of a window to its end and spoils the window if the game was behind anything at any check. - Before a window the kit asks the user, with a beep, to go back to the game and waits up to two minutes. - What was in front is kept only as a category (a Jarvis process, a console window, Explorer, another app), never an app name. Results: with the game in front, a busy Jarvis cost 0.2 % of the average fps and 3.3 % of the 1 % low with no frames over 50 ms, so by the pre-registered rule nothing is added and yielding is not adopted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
94 KiB
94 KiB