feat(deploy-kernel): prestage hit/miss verdicts — make the silent cost loud #2064

Merged
pipeline-bot merged 1 commit from feat/prestage-visibility into trunk 2026-08-18 14:24:30 +00:00
Owner

Times every kstage and prints a mode-aware hit/miss verdict; a mode=roll miss is the ~3min/node suspect behind 10.5-vs-7 min legs. Measurement rides the next real roll.

Times every kstage and prints a mode-aware hit/miss verdict; a mode=roll miss is the ~3min/node suspect behind 10.5-vs-7 min legs. Measurement rides the next real roll.
feat(deploy-kernel): prestage hit/miss verdicts — make the silent cost loud
All checks were successful
pipeline/ci CI green @ 67c17c657ae9
67c17c657a
The sf36 workers roll spent ~10.5 min per serialized node while the
step metrics floor says ~7 (roll-node 4.2-5.7m + green 1.3-3.2m). The
suspect gap is pre-stage misses: the prestage fan-out tolerates
failure by design (continueOn), and a missed node repays the full
image pull inside the serialized window with NOTHING recording that
it happened.

Every kstage now times  and prints
 —
in prestage mode a long stage is the machinery working; a mode=roll
miss is the regression signal. Next real roll answers the question
from evidence instead of theory.
sean force-pushed feat/prestage-visibility from 67c17c657a
All checks were successful
pipeline/ci CI green @ 67c17c657ae9
to 9d4f0b6665
All checks were successful
pipeline/ci CI green @ 9d4f0b666538
2026-08-18 14:23:45 +00:00
Compare
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
sean/pipelines!2064
No description provided.