[codex] Add quiet target leases for benchmarks#75
Merged
Conversation
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.
Summary
Adds benchmark quiet-mode support for worker sessions:
target_quietlocksrequest_quiet_target/release_quiet_targetMCP tools to workers and follow-upsWhy
Benchmark work sometimes needs a genuinely quiet machine for accurate timing, but the fleet should still run multiple sessions per target outside those measurement windows. This makes quiet mode temporary and explicit instead of lowering target capacity permanently.
Validation
go test ./internal/orch -run 'TestQuietTarget|TestMCPSurfaces' -count=1\n-go test ./internal/orch ./internal/store ./internal/model ./internal/api