This is awesome. Didn't know about this setting. Is there a reason why we don't set nodelay to true by default? It seems that even the [continuous] _changes feed will do *much* better with this setting, notifying the listeners immediately without any buffering. True?
One more Q: After changing this and if I invoke _restart, will the settings take into effect? Thanks, K. --- http://blitz.io @pcapr On Tue, Aug 16, 2011 at 9:36 PM, Filipe David Manana <[email protected]> wrote: > On Tue, Aug 16, 2011 at 9:18 PM, John Cheng >>> Have you tried setting server's socket options, in the .ini config, as >>> I suggested before? (setting nodelay to true) >>> >>> >> You know I really thought I had tried that last night without seeing a >> difference. I just tried it again right now and saw that was indeed the >> source of my problem. Boy do I feel embarrassed right now. >> >> Thank you for your patience! > > Np. > Yes, default is false. For me, on Linux 32 bits at least, nodelay set > true makes a huge difference as well. > > >> >> Just for the record, this is the setting >> >> socket_options = [{recbuf, 262144}, {sndbuf, 262144}, {nodelay, true}] >> >> In default.ini it is commented out, and I assume by default nodelay is set >> to false. >> > > > > -- > Filipe David Manana, > [email protected], [email protected] > > "Reasonable men adapt themselves to the world. > Unreasonable men adapt the world to themselves. > That's why all progress depends on unreasonable men." >
