[DH-3] tweaking core pool sysctl tcp settings... again #5676
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.
after a year, and after seeing more SYN flooding... as well as reading more and understanding the variables a bit more i wanted to revisit #4488
the big takeaways here are:
this can safely be merged at any time, and whatever comes out of this PR will be used when we create a new core pool w/more cpu (as 8 cores isn't enough when you run as many hubs as we do on a node) and the same ram.
a bunch of these settings tweaks came from https://fasterdata.es.net/host-tuning/linux/#toc-anchor-2
@ryanlovett @consideRatio @yuvipanda any thoughts?