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).
7 lines
142 B
JSON
7 lines
142 B
JSON
{
|
|
"window_ms": 10000.0,
|
|
"system_cpu_ms": 19850.0,
|
|
"compositor_cpu_ms": 9500.0,
|
|
"system_cpu_pct": 198.5,
|
|
"compositor_cpu_pct": 95.0
|
|
} |