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.
14 lines
515 B
Nix
14 lines
515 B
Nix
# Spike-local toolchain for route 001a. Rust stays out of the repository flake
|
|
# on purpose: this shell is the only place this spike gets rustc and cargo.
|
|
#
|
|
# Do not set WAYLAND_DISPLAY or XDG_RUNTIME_DIR here. The run commands in
|
|
# README.md set WAYLAND_DISPLAY to the absolute socket path. Pointing
|
|
# XDG_RUNTIME_DIR at /run/hypr-stream makes libwayland reject the runtime dir.
|
|
{ pkgs ? import <nixpkgs> { } }:
|
|
pkgs.mkShell {
|
|
packages = with pkgs; [
|
|
rustc # 1.98 from the machine's nixpkgs
|
|
cargo
|
|
];
|
|
}
|