test(process): attribute session spawn overhead (#366) - #383
Merged
Merged
Conversation
…:process::Command Attributes #366: a bare session tracks std; kill_when_owner_dies and a best-effort priority each add sub-millisecond-to-millisecond cost because the substrate installs them in pre_exec (fork+exec instead of posix_spawn).
zackees
force-pushed
the
perf/session-spawn-366
branch
from
September 29, 2026 20:30
de42a0e to
03f9ee4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an ignored measurement (
tests/process/session_spawn_cost.rs, a module of the existing process category) comparing a session spawn tostd::process::Commandper option.Finding: a bare session is within ~0.2 ms of std;
kill_when_owner_diesand best-effort priority each add ~0.4-0.8 ms because the substrate installs them inpre_exec(fork+exec instead of posix_spawn). Admission is free. The fix belongs in running-process: zackees/running-process#1248.Refs #366 (left open until running-process lands the fix and zccache re-measures).