Files
hyprland-headless-stream-pl…/spikes/capture-speed/results/final-motion/grim.output-jpeg.run2.stdout
T
Hermenix 36efa316fd spike: the verdict, the table, the chart -- in-process pywayland wins on zwlr-screencopy
Four routes measured on one frozen contract at one session's container size, with
RAM and CPU as first-class results: in-process pywayland is ~1.5x faster (78 vs
117 ms), uses ~2.8x less of our own CPU, and nearly halves the compositor's
per-frame CPU (67 vs 116 ms). grim-rs buys nothing and costs 746 MB RSS.
ext-image-copy-capture measures identical to screencopy and appears in a
compositor crash stack, so the deprecated-but-working protocol is the pick.

Also fixes the client's unclean exit (pywayland teardown segfaulted after the
result was printed, 16 times, one batch coinciding with a compositor crash).
2026-10-11 17:08:13 +00:00

2 lines
761 B
Plaintext

{"route": "grim-subprocess", "language": "python", "protocol": "zwlr-screencopy-v1 (grim's client)", "output": "hh-chromium-gqkxz3", "geometry": [1280, 720], "mode": "jpeg", "warmup": 10, "frames": 200, "frame_ms": {"min": 67.203, "p50": 118.52, "mean": 124.224, "p95": 185.591, "max": 299.044}, "fps_sustained": 8.05, "wall_ms": 25182.14, "bytes_p50": 130590, "persistent": false, "notes": "one grim process per frame, fork and encode inside the timed span; territory: --output; jpeg q80", "cpu_ms_per_frame": 5.05, "rss_peak_mb": 18.45, "rss_peak_kb_raw": 18896, "system_cpu_ms_per_frame": 250.75, "compositor_cpu_ms_per_frame": 117.75, "machine_cpu_pct": 199.1, "machine_cpu_pct_of_all_cores": 99.6, "frames_bytes_allocated_p50": null, "resource_notes": ""}