Windows 200ms delay issue.

[JacksonTian]

When I deploy the hello world program on Windows server, and access it with Windows, it always lead 200+ms delay.

var http = require('http');
http.createServer(function (req, res) {
  res.writeHead(200, {'Content-Type': 'text/plain'});
  res.end('Hello World\n');
}).listen(1337);
console.log('Server running at http://127.0.0.1:1337/');

I search the issue, it seems a typical issue to Windows.

[piscisaureus]

@JacksonTian
I can't replicate this. If you want us to fix this issue you need to be much more specific than this. Tell me about windows and node versions, your test setup, and how you're measuring this 200ms delay.

[kvanbere]

We have an issue like this with node too and our websockets. We ended up dropping node and just using Java because we couldn't figure it out.

The delay only happened when the host was Windows 7. It went away with Windows 8.

[piscisaureus]

The fact that you explicitly say "200ms" makes me think that you are seeing the effects of the 200ms delayed ACK timer (aka Nagle's algorithm) in windows. Have you tried disabling it with Socket#setNoDelay?

[clintwood]

I'm not sure if this is related but I had a similar issue (although it was longer than 200ms) on the initial/ first request when the server is started (Win7 or 8) and especially when accessing via a client on the same machine (server/desktop). For me the issue was due to antivirus interference - in my case specifically Avg's Identity & Web protection features which I have now turned off. Before discovering the antivirus interference issue I tried to tweak Windows Nagle's algo settings etc but that didn't help.