test(proto): Add regression test from scenario that lead to infinite loss timer loop#562
Draft
test(proto): Add regression test from scenario that lead to infinite loss timer loop#562
Conversation
|
Documentation for this PR has been generated and is available at: https://n0-computer.github.io/noq/pr/562/docs/noq/ Last updated: 2026-04-02T12:47:47Z |
Performance Comparison Report
|
| Scenario | noq | upstream | Delta | CPU (avg/max) |
|---|---|---|---|---|
| large-single | 5842.7 Mbps | 8023.0 Mbps | -27.2% | 96.4% / 98.2% |
| medium-concurrent | 5837.5 Mbps | 7616.2 Mbps | -23.4% | 95.8% / 97.6% |
| medium-single | 3875.4 Mbps | 4592.6 Mbps | -15.6% | 95.5% / 97.9% |
| small-concurrent | 4051.7 Mbps | 5190.3 Mbps | -21.9% | 97.0% / 99.6% |
| small-single | 3629.4 Mbps | 4677.2 Mbps | -22.4% | 96.0% / 98.5% |
Netsim Benchmarks (network simulation)
| Condition | noq | upstream | Delta |
|---|---|---|---|
| ideal | N/A | 4036.8 Mbps | N/A |
| lan | N/A | 810.4 Mbps | N/A |
| lossy | N/A | 55.9 Mbps | N/A |
| wan | N/A | 83.8 Mbps | N/A |
Summary
noq is 22.8% slower on average
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.
Description
For now just an added regression test that reproduces a pretty bad scenario where we start to hot-loop on the loss detection timer timing out and us re-setting it to a value in the past (and thus immediately-retriggering it) indefinitely.