Repository navigation
Conversation
SPIN_LANE_DIAG=1 replaces the rows with sshd at LogLevel DEBUG1 and logind at debug, and prints the first boots' journal lines with their offsets from accept: which step the ~55 ms before authentication and the ~29 ms before logind's new session are made of. Logging inflates what it logs; these say what a hop is, not what it costs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The lane's drop-in took logind's default dependencies away, not its varlink socket's: logind was ready ~230 ms into the boot, behind sysinit.target and udevd (lab 44557605832), and the first login's pam_systemd waited ~32 ms for it (lab 44557162195). SPIN_LOGIND_EARLY=1 adds the socket without default dependencies, and that with modprobe@drm masked, which logind is ordered after. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The lane took logind's default dependencies away, not its Varlink socket's, and the service waits for its socket: logind was ready ~230 ms into the boot behind udevd, and the first login's pam_systemd waited ~32 ms for it. Without them, 20 boots of each on the bench: that hop 24.5/41.8 -> 15.8/22.7 ms, the first login 332/355 -> 328/337. build.sh asserts the drop-in like the lane's others; the experiment rows go. 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.
boot:login-lane's diagnostic rows (SPIN_LANE_DIAG=1: sshd at DEBUG1, logind at debug, each boot's journal with offsets from accept) explain the first login's own ~130 ms:sshd@takes ~11 ms, OpenSSH 10's three execs (sshd→sshd-session→sshd-auth) ~12, and loading PAM's modules cold 8.3, against 0.9 at the second login. ML-KEM is 3.5.sysinit.targetand udevd, ready ~230 ms into the boot (boot:waits TARGET=systemd-logind.service). The second login's hop is 1 ms.systemd-logind-varlink.socket.d/20-lane.confdrops the socket's default dependencies, as10-lane.confalready does for the service. Bench fleet, v20261119.01, 20 boots of each, interleaved (labs 44558035927, 44558053261):The p95 gains most. The p50 moves little because logind starting sooner takes the CPU sshd was starting on. Masking
modprobe@drmadded nothing (327/345) and is indocs/log.md§4.image/build.shasserts the drop-in, as it does the lane's others.boot:ssh-firstputs it in the "as this branch" row.boot:logindpasses on the built image.🤖 Generated with Claude Code