[SWE] Make Gym startup metrics optional and atomic - #22
Draft
seonjinn wants to merge 3 commits into
Draft
Conversation
Signed-off-by: seonjinn <sna@nvidia.com>
Signed-off-by: seonjinn <sna@nvidia.com>
Signed-off-by: seonjinn <sna@nvidia.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.
Problem
We need to understand where SWE rollout startup time is spent: connecting to NeMo Gym, creating the runtime, or initializing the agent.
The existing timers write into a NeMo Gym metrics file. This makes standalone OpenHands runs fragile when the file is not configured.
High-level change
This PR makes the existing startup timers safe and optional.
It keeps the existing phase boundaries and timer names. It only changes how their results are published:
NEMO_GYM_METRICS_FPATHis set;Expected impact
This is an observability change, not a rollout speedup by itself. It gives us reliable phase-level data needed to find and validate Init and Framework overhead reductions.
It does not change agent commands, retries, controller behavior, or runtime setup.
Change Type
Release Notes