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

[Feature Request] Change default connection listen backlog to 512 #203

Closed
druchoo opened this issue Jul 13, 2016 · 4 comments
Closed

[Feature Request] Change default connection listen backlog to 512 #203

druchoo opened this issue Jul 13, 2016 · 4 comments

Comments

@druchoo
Copy link

druchoo commented Jul 13, 2016

Per @redbaron in #186 512 is a reasonable default value for connection listen backlog.

..setting it to 512 will do no harm whatsoever, but would make it more reliable against short burst of new incoming connections. setting it to 3 is just silly and have no reason to exist

@grobian
Copy link
Owner

grobian commented Jul 13, 2016

http://www.linuxjournal.com/files/linuxjournal.com/linuxjournal/articles/023/2333/2333s2.html and
http://veithen.github.io/2014/01/01/how-tcp-backlog-works-in-linux.html
both seem to suggest 512 is not a good default, since 128 appears the default max for Linux. (sysctl net.core.somaxconn tells me at least).

@grobian
Copy link
Owner

grobian commented Jul 13, 2016

So, perhaps 32 is a bit more conservative default (still much better than 5 if you need it)?

@druchoo
Copy link
Author

druchoo commented Jul 13, 2016

I'm by no means an expert. So i'll defer to others one this. But anything higher than 5 is probably better.

@grobian
Copy link
Owner

grobian commented Jul 13, 2016

agreed

@grobian grobian closed this as completed Jul 13, 2016
piotr1212 pushed a commit to piotr1212/puppet-carbon_c_relay that referenced this issue Aug 19, 2016
piotr1212 pushed a commit to piotr1212/puppet-carbon_c_relay that referenced this issue Oct 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants