fix(stresstest): Report true elapsed time and metrics#370
Merged
Conversation
…ation When a backlog of requests builds up, tasks may finish after the configured duration expires. Using the hardcoded duration for metrics reporting produced incorrect ops/s and throughput numbers. This tracks the real wall-clock time from start until all tasks complete and uses that for reporting. Also moves the semaphore acquire before reading metrics to ensure all in-flight tasks are reflected.
lcian
changed the title
jan-auer
approved these changes
Mar 12, 2026
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
2 participants
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.
This fixes 2 issues that would happen when the stresstest is firing too many requests and a backlog would build up.
These would report incorrect throughput and bandwidth numbers.
They're most relevant for short tests, as things would smooth out over time in longer ones. They're also relevant for tests where a single operation takes a long time (such as the gaming ones).