bench: sparse stderr progress with elapsed and ETA - #167
Merged
Conversation
A casa/sparrow corpus run can take minutes with no output until the final table. Print a short stderr line at start, each 5% of work, and at most once per 15s, including remaining time. Stdout stays the p50/p95 report.
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
1 participant
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.
Why
A packed casa (~4k keys × 10 passes) or sparrow (3000-key load/refresh) run can sit silent for minutes. Need a sense of how far through the current suite we are without flooding stdout (the p50/p95 table).
What
rbitcoin-bench: casa electrum 128/40960 (0%) elapsed 12s left ~17mload→refresh(→txsif--fetch-txs).