perform send / receive buffer increases when setting up the connection #3949
Conversation
This file contains 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
The UDP send and receive buffer is now increased when calling OptimizeConn.
Codecov Report
@@ Coverage Diff @@
## master #3949 +/- ##
==========================================
- Coverage 82.86% 82.78% -0.08%
==========================================
Files 146 146
Lines 14622 14622
==========================================
- Hits 12116 12104 -12
- Misses 2015 2024 +9
- Partials 491 494 +3
|
MarcoPolo
approved these changes
Jul 12, 2023
marten-seemann
added a commit
that referenced
this pull request
Jul 12, 2023
#3949) The UDP send and receive buffer is now increased when calling OptimizeConn.
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.
The UDP send and receive buffer is now increased when calling OptimizeConn.
This should be the easiest fix for #3947, in the sense that it doesn't lead to any API changes, and we can include it in a v0.36.2 patch release.