Skip to content
This repository has been archived by the owner on May 22, 2020. It is now read-only.

Image: We should tweak our sysctls #261

Closed
justinsb opened this issue Dec 2, 2016 · 4 comments
Closed

Image: We should tweak our sysctls #261

justinsb opened this issue Dec 2, 2016 · 4 comments
Labels
imagebuilder lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@justinsb
Copy link
Contributor

justinsb commented Dec 2, 2016

sysctl -w net.core.somaxconn=32768

Thanks @aledbf

@aledbf
Copy link

aledbf commented Dec 2, 2016

# Increase the number of connections
net.core.somaxconn=32768

# Increase number of incoming connections backlog
net.core.netdev_max_backlog = 5000
 
# Maximum Socket Receive Buffer
net.core.rmem_max = 16777216
 
# Default Socket Send Buffer
net.core.wmem_max = 16777216
 
# Increase the maximum total buffer-space allocatable
net.ipv4.tcp_wmem = 4096 12582912 16777216
net.ipv4.tcp_rmem = 4096 12582912 16777216
 
# Increase the number of outstanding syn requests allowed
net.ipv4.tcp_max_syn_backlog = 8096
 
# For persistent HTTP connections
net.ipv4.tcp_slow_start_after_idle = 0
 
# Increase the tcp-time-wait buckets pool size to prevent simple DOS attacks
net.ipv4.tcp_tw_reuse = 1
 
# Allowed local port range
net.ipv4.ip_local_port_range = 10240 65535

# Max number of packets that can be queued on interface input
# If kernel is receiving packets faster than can be processed
# this queue increases
net.core.netdev_max_backlog = 16384

# Increase size of file handles and inode cache
fs.file-max = 2097152

@fejta-bot
Copy link

Issues go stale after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 19, 2017
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 18, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
imagebuilder lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants