-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Server Keep-alive and timeout redesign #339
Labels
Comments
I personally switched all my production systems to SO_KEEPALIVE |
basically we should register one timer and manage callbacks in |
Pushing timer into |
-1 for |
Merged
Fixed by #702 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now we register keep-alive and timeout timers for each connection. And that is very expensive. Also both timers are in seconds. So instead we should use one global timer, seconds base. And manage keep-alive and timeout ourselfs.
It might be useful to use same approach for client as well.
The text was updated successfully, but these errors were encountered: