Repository navigation
fix(analyze): treat a load-generator burst as an invalid step - #13
Merged
Merged
Conversation
A SIPp that falls behind its schedule later sends the calls it owes in one burst. On Routr's 2026-11-04 calibration that burst (29,674 calls in 10 s at a 2,100/s target) made the Go EdgePort's 2,100 step fail and was published as its limit, though the EdgePort handled 5,000/s without a retransmission in a lab run. A step that placed more than 105% of the offered rate is now invalid, so the verdict is inconclusive instead of a false limit.
This was referenced Nov 4, 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
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.
A SIPp that falls behind its schedule later sends the calls it owes in one burst. On Routr's 2026-11-04 calibration that burst (29,674 calls in 10 s at a 2,100/s target) failed the Go EdgePort's 2,100 step and was published as its limit, though the EdgePort handled 5,000/s with no retransmission in a lab run on the same droplet size. A step that placed more than 105% of the offered rate is now invalid, so the verdict is inconclusive instead of a false limit.
Verify:
npm test(new case: "should be inconclusive when SIPp placed 110% of the offered rate").🤖 Generated with Claude Code