Merged
Conversation
we may fail to ACK something (Cubic congestion algorithm 1ms later kind of thing)
nextdns with QUIC is unreliable due to a possible mistake with post quantum key exchange algorithm (either us or them... or both!!)
potential performance boost for QUIC/UDP layer. Reducing syscalls.
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.
2.17.900 (2026-03-03)
This should increase QUIC/UDP performances in high throughput networking environment (very-fast NIC).
Expect no more than 10 to 20% improvement usually.
AsyncPoliceTrafficscheduler implementation in order to not penalize fast servers.expected bytes-like object, not int#318)