Skip to content

The load test asks for a clear rise in throughput, not a multiple - #26

Merged
wasabii merged 1 commit into
mainfrom
feature/load-test-bar
Oct 4, 2026
Merged

wasabii merged 1 commit into
mainfrom
feature/load-test-bar

Conversation

@wasabii

@wasabii wasabii commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

Carried over from after #25 merged.

On a slow shared build machine (the macOS x64 runner) the overhead of each call takes most of what a higher limit allows: in one run the limit rose 2 to 6 and throughput 1.46 times, under the 1.5 the test asked for, where a desktop shows 2.7. The claim is that the rise bought throughput; 1.2 says so and a flat result does not. The three runs since passed on that margin by luck, not a fix.

On a slow shared build machine the overhead of each call takes most of what a higher limit allows:
the limit rose 2 to 6 and throughput 1.46 times, under the 1.5 the test asked for, where this
machine shows 2.7. The claim is that the rise bought throughput; 1.2 says so and a flat result
does not.
@wasabii
wasabii merged commit b40b83e into main Oct 4, 2026
25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant