-
Notifications
You must be signed in to change notification settings - Fork 107
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
[Question] What is connection listen backlog? #186
Comments
I thought I answered this in length, apparently not. long story short, the setting has no impact on performance. |
has it? 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 |
If you want to advocate changing the default to 512, then go ahead, no reason not to change it if there is a good reason for it. File a new issue for it. |
My question has been answered and created #203 to increase default value to 512. Closing issue. http://veithen.github.io/2014/01/01/how-tcp-backlog-works-in-linux.html for further reading on connection listen backlog |
# -B connection listen backlog, defaults to 3
#143
Can someone please explain what connection listen backlog is and elaborate on how changing this setting impacts performance?
The text was updated successfully, but these errors were encountered: