-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Change default backlog size and make configurable #8
Comments
pietermees
added a commit
to pietermees/turbo-net
that referenced
this issue
Mar 18, 2018
Match Node's default backlog of 511 sockets (see https://nodejs.org/dist/latest-v9.x/docs/api/net.html#net_server_listen) This helps address mafintosh#8 and mafintosh/turbo-http#12
mafintosh
pushed a commit
that referenced
this issue
Mar 18, 2018
Match Node's default backlog of 511 sockets (see https://nodejs.org/dist/latest-v9.x/docs/api/net.html#net_server_listen) This helps address #8 and mafintosh/turbo-http#12
It's 511 now (you've fixed that :)) - we should still make it configurable |
Yes, and I guess we could change that TODO in the code from researching to making it configurable? Then users that don't like the default can do their own research ;) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sending a lot of simultaneous requests causes the backlog to overflow and new connection attempts to be rejected. (see mafintosh/turbo-http#12)
This is caused by the fixed default backlog size of
5
athttps://github.com/mafintosh/turbo-net/blob/master/src/turbo_net.c#L190.Node's default is
511
(see https://nodejs.org/dist/latest-v9.x/docs/api/net.html#net_server_listen)Node's
listen
also accepts a parameter to override the backlog size.The text was updated successfully, but these errors were encountered: