Record your screen, ship a demo. Free and open-source, GPU-accelerated, no watermarks, no subscriptions. Windows, macOS, Linux. Actively maintained.
TypeScript cross-platformelectronffmpegopen-sourceproduct-demorustscreen-capturescreen-recorderscreen-recordingscreen-studioscreencastspeech-to-texttypescriptvideo-editingvideo-editorwaylandwgpuwhisper
docs(testing): the 60 Hz steps back come from slot reuse, not from main
EtienneLescot298422327e9c
diff --git a/technical-documentation/testing/performance-ab.md b/technical-documentation/testing/performance-ab.mdindex a5a8d683d..68c98458c 100644--- a/technical-documentation/testing/performance-ab.md+++ b/technical-documentation/testing/performance-ab.md@@ -43,7 +43,7 @@ log of every comparison run so far. The scripts live in [`scripts/perf-ab/`](../|---|---|---|---|---|| 1 | Startup to a ready HUD +47 ms (625 → 672 ms). Editor open unchanged (1143 → 1136 ms) | Startup: regression, p < 0.001. Editor open: retracted | No single commit found, bisection to rerun on a quiet machine. +18 ms before the HUD page starts, which is not main-process JavaScript; +12 ms of CPU in the HUD's first render, spread over a dozen modules | Try a HUD entry of its own, without the editor's code, and measure it || 2 | Heavy preview: 87 → 102 paints later than 25 ms per 30 s (+17%) | Within noise, p ≈ 0.2 | Both builds land in a slow mode (paint p95 28.5 ms instead of 22 ms) in about half the sessions: 2.0.0 6 of 12, main 7 of 12. The mode follows the session, not the build. | Find what sets the mode |-| 3 | At 60 Hz the preview paints 51 to 58 frames a second, and the cursor steps backwards 24 to 153 times in 18 s (2.0.0 median 31, main 53) | Pre-existing, both builds; main's count within noise | Not established. First hypothesis: the compositor's own 60 Hz pacing beats against the display's 60 Hz vsync, so a frame composed for one instant shows a vsync early or late | Pace the preview on the display's vsync, measure at 60 Hz |+| 3 | At 60 Hz the preview paints 51 to 58 frames a second, and the picture and the cursor step back one frame tens of times in 18 s | Pre-existing, both builds: over 8 pairs main has more steps back 4 times, 2.0.0 3 times | The shared-texture ring wrote a slot again as soon as Chromium released it, before the GPU had copied it into the canvas: the painted frames' times never go back, the screen does | Fixed in #1285: the slot is handed back 40 ms later, no step back at 60 or 280 Hz || 4 | GPU process dedicated memory, one traced session each: 0.8 GB (2.0.0) and 1.4 GB (main) at 11 s of playback, 9.8 GB and 12.8 GB at 2 min | Pre-existing, both builds | Grows linearly with playback, so something per frame is kept: the shared-texture preview path is the first suspect | Trace the shared frames' lifetime |#### Preview, light project (3 sessions each)