increase default conntrack buffer size #2739
Merged
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 figure is based on our experience of running scope probes in production systems. Below this we see a lot of "conntrack stderr:WARNING: We have hit ENOBUFS! We are losing events."
2opremio
approved these changes
Jul 25, 2017
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 figure is based on our experience of running scope probes in production systems. Below this we see a lot of "conntrack stderr:WARNING: We have hit ENOBUFS! We are losing events."
There is no downside to a larger buffer size other than, presumably, higher memory use, but since scope probes typically weigh in at >100M RSS, adding a few extra M bufferspace is hardly a concern.