-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Adapt the socket receive buffer size to traffic #11491
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
lpgauth
wants to merge
5
commits into
erlang:master
Choose a base branch
from
lpgauth:esock-adaptive-rcvbuf
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+182
−4
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
09bd046
erts: Adapt the socket receive buffer size to traffic
lpgauth 3e784a0
erts: Keep the configured esock rcvbuf in rBufSz
lpgauth 50da2f5
erts: Shrink the adaptive esock rcvbuf via an EWMA
lpgauth fbf5e58
erts: Cap the adaptive esock rcvbuf at 256 KB
lpgauth a582f34
kernel: Test the adaptive esock rcvbuf
lpgauth File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes me think that this buffer will essentially be really hard to ever shrink, it takes 32 consecutive reads under a quarter of the buffer size to ever shrink, so on a mixed-sized packets connection it might virtually never trigger. It also means an idle socket would not shrink either, and once you have 10k sockets not shrinking you have 10GB of RAM wasted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replaced the counter with an EWMA of the read sizes, see the other thread. On the idle point: the descriptor buffer is only kept when the last read used less than 75% of it, otherwise recv_create_bin hands it off to the returned binary, so an idle socket pins at most one buffer, now at most 256 KB. Freeing it on shrink could be a follow-up.