-
Notifications
You must be signed in to change notification settings - Fork 250
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
Is there anyway to disable nagle algorythm from here? #41
Comments
Hmm, looks like there's been a misunderstanding. The Node.js docs say:
Because it says "noDelay defaults to true", I thought that it was enabled by default, and that "By default TCP connections use the Nagle algorithm" is more of a generic statement about TCP connections. Now that I've checked it again, it doesn't look like it's doing it by default after all. What it's really saying is that if you call |
It probably depends on your internal network and machine settings, though, since we never had this issue. |
I've released 2.4.0 with TCP_NODELAY. Please run |
Disable Nagle fix my debugging problem. Thanks. |
I found the remote debug latency is really big and I am trying to disable Nagle algo from both server and client side for STF. Thanks.
The text was updated successfully, but these errors were encountered: