Skip to content
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

[DH-3] tweaking core pool sysctl tcp settings... again #5676

Merged

Conversation

shaneknapp
Copy link
Contributor

@shaneknapp shaneknapp commented Apr 11, 2024

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:

  1. we have more ram (64G n2-highmem-8 vs 8G n2-standard-8), and should consider allocating a bit more to the kernel for tcp
  2. our max number of connections (!!!!) was only 1024 (!?!?!?!). i increased this to 4096 (somaxconn) which i think might help
  3. our nodes look to have lots and lots of bandwidth, so let's take advantage of that! (https://cloud.google.com/compute/docs/network-bandwidth#egress)

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?

@shaneknapp shaneknapp merged commit e480022 into berkeley-dsep-infra:staging May 8, 2024
21 checks passed
@shaneknapp shaneknapp deleted the tweak-core-pool-sysctl branch May 8, 2024 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant