Skip to content

fix(OMN-18024): retire the dev-system instance id from the preflight docstring #3313

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jonahgabriel merged 1 commit into from
Sep 8, 2026
Merged

fix(OMN-18024): retire the dev-system instance id from the preflight docstring #3313

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions src/omnibase_infra/runtime/entrypoint_preflight.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,10 +12,10 @@
* ``exec onex-runtime`` (the kernel itself) -- 48.6 s
* total before any wiring work at all: **292.0 s**

Measured live on 2026-09-06 from the onex-dev ``omninode-runtime`` container
(dev-system cluster ``i-06169517a92b45f86``), container start 21:34:27Z: 551 s
of an 1124 s boot elapsed before the FIRST subscription was attempted, 292 s of
it in those four interpreter starts. The same phase on the .201 dev lane is
Measured live on 2026-09-06 from the onex-dev ``omninode-runtime`` container on
the dev-system cluster, container start 21:34:27Z: 551 s of an 1124 s boot
elapsed before the FIRST subscription was attempted, 292 s of it in those four
interpreter starts. The same phase on the .201 dev lane is
~8x faster on the same code, because the onex-dev container runs at
``requests.cpu 100m`` on a node whose CPU limits are 547 % overcommitted — the
signature of ~0.05 effective cores paying four cold imports.
Expand Down
Loading