Repository navigation
Add opt-in bounded receive-window auto-tuning - #101
Open
DeveloperKubilay wants to merge 1 commit into
Open
DeveloperKubilay wants to merge 1 commit into
DeveloperKubilay wants to merge 1 commit into
Conversation
DeveloperKubilay
marked this pull request as ready for review
October 21, 2026 18:24
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.
Proposes an optional receive-window controller for applications with changing receive demand. Applications explicitly enable it per readable stream and choose minimum/maximum byte bounds; existing applications keep their fixed sliding window.
The controller estimates a target from application-consumed bytes and smoothed RTT, with a minimum sample period, bounded growth/shrinkage and idle handling. It never revokes previously advertised offsets or increases the configured connection budget. Credit callbacks run outside the receive monitor to avoid blocking a producer that immediately delivers more data. The accompanying document describes API behavior, estimator limits and flow-control semantics.
This is a consumption-rate heuristic, not a physical bandwidth measurement. It does not add pacing, BBR, PMTU discovery or application packet buffering. The two reliability fixes are submitted separately so this API/algorithm proposal can be reviewed independently.
Validation on current master (
101c733d), JDK 21 / Windows:NewRenoCongestionControllerTest.congestionAvoidance. The congestion-avoidance case passes in the focused run.The public API and estimator policy are proposed for review before considering release inclusion. No library version or release workflow changes are included.
Fork CI: the complete
./gradlew buildpassed on Linux / JDK 17 with the upstream workflow and no test exclusions: https://github.com/DeveloperKubilay/kwik/actions/runs/39651942299. Upstream PR checks remain separate.