fix: clean up Docker verifier containers after runs - #28
Open
DeSitterUniverse wants to merge 1 commit into
Open
Conversation
DeSitterUniverse
marked this pull request as ready for review
August 20, 2026 19:01
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
Clean up BenchLocal-owned Docker verifier containers when the final run lease is released. This is done to reduce RAM and resource usage from containers that are no longer needed when benchmarking.
Covered paths:
Implementation
Why
A verifier container is a short-lived benchmark dependency, but it previously remained running after a run completed. This retains Docker/Node process memory until manually stopped.
Measured local impact:
The StructOutput-15 measurement used 1,014 Docker memory samples during a 33m44s run. The container peaked at 12.13 MiB, then no container remained after finalization. Potential memory savings are higher than tested.
Validation