Repository navigation
boot/systemd: measure PID 1's own steps; systemd experiments in the lab - #283
Merged
Merged
Conversation
… job image/systemd builds an experiment's patch when SYSTEMD_EXPERIMENT names one; experiments/pid1-marks makes PID 1 append its monotonic clock to /run/spin-pid1-marks after each step of manager_startup and do_queue_default_job. boot:waits puts SPIN_SYSTEMD_DEBS into each overlay and gives each step's p50; lab.yml's systemd_experiment builds the packages on the runner before anything is measured. The ~32 ms gap had been "explained, not removable" from one debug-logged boot. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…n unit_load Wall time well above PID 1's own CPU time in a step is waiting - on the disk or for a CPU - rather than parsing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Kept as tooling for the next systemd experiments:
image/systemdappliesexperiments/<name>.patchwhenSYSTEMD_EXPERIMENTnames one. The image never does.lab.ymlsystemd_experimentbuilds that systemd on the runner, before anything is measured, andboot:waitsputs it into each overlay (SPIN_SYSTEMD_DEBS).experiments/pid1-marks.patchmakes PID 1 append its monotonic clock, its own CPU time, the units loaded and the time inunit_loadafter each step ofmanager_startupanddo_queue_default_job.boot:waitsprints each step's p50.Bench fleet, 10 boots (lab 44561762624):
default.targetreachesThe ~30 ms gap after the unit load is unit loading, ~0.11 ms of CPU per unit. It is not the transaction, which 11-13's single debug-logged boot had named.
docs/log.mdand the comment inwaits_probe_test.goare corrected. Next: a per-unit load profile, then a row that deletes the unit files no boot here runs.🤖 Generated with Claude Code