Commit Graph
4 Commits
Author SHA1 Message Date
Hermenix e2d9cb7dd4 spike: record what crashes the compositor, and the copy probe that explains grim-rs
CRASH-FINDING.md is the delegated session's sharper version of the crash result:
hold a live ext capture session on a session's output, kill the session, call
create_frame -> SIGSEGV in CScreenshareFrame::transform(). That is a reproducible
trigger, not a correlation, and it is why ext-image-copy-capture was measured and
then not adopted.

copyout_probe.py prices the per-frame allocate/copy/swizzle that grim-rs's API
forces: 2.2 ms of client time, which is nowhere near its 46 ms deficit against the
in-process route -- so the difference is buffer reuse, not language.
2026-10-11 22:47:28 +00:00
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
Hermenix bf0667303e spike: --resume for the runner, and run the matrix from a transient unit
Two attempts were reaped mid-run by agent lifecycle cleanup (exit 143 with no
error line); a nix-shell process tree of tens of minutes belongs in a systemd
transient unit, not an agent background process. --resume skips any cell whose
result file already exists, so a kill costs the cell in flight and nothing else.
2026-10-11 16:25:38 +00:00
Hermenix da14048010 spike: measure grim, raw pywayland and grim-rs on one contract, with RAM and CPU
The question is which capture route to ship for live streaming and agent eyes.
Speed alone does not decide it, so every route now also reports producer CPU and
RSS, machine CPU from /proc/stat, the compositor's own CPU, and a per-frame
buffer footprint -- all sampled around the measured loop, with an idle control
sample so an animating page's cost is not attributed to the capture.

The baseline forks a process per frame and spends 95% of each frame waiting, so
the interesting finding is not which route is faster but which one leaves the
compositor able to do its job: in-process acquisition roughly halves the
compositor's per-frame CPU even though the machine saturates either way.
2026-10-11 15:45:09 +00:00