Thanks! This was puzzling me; I had found a few references to Nagle in
searching but it didn't seem to make sense. TCP_CORK appears to be already
used which I thought was in essence manual management of the packet
delays, but I guess not. Yay, linux?
In any case, setting the option correctly
Hi Jeff,
I found the problem: One has just to tell Linux to turn the delay off.
What sounds as a joke can be done in the config file as shown below,
which turns off the good old Nagle algorithm for incoming packages
on the keep-alive socket. This reduces the delay seen from poll()
substantially
On 30.11.18 21:17, Jeff Rogers wrote:
Ok, thickening the plot a little bit - if I enable adp parsing and
serve the exact same file as adp, the delay on localhost goes away.
So, something weird with plain file handling on loopback?
i tested now with debian-sid and can confirm the behavior, whi
Ok, thickening the plot a little bit - if I enable adp parsing and serve
the exact same file as adp, the delay on localhost goes away. So,
something weird with plain file handling on loopback?
-J
On 11/30/2018 11:51 AM, Jeff Rogers wrote:
So really, this appears to be NOT a naviserver iss
Hi Gustaf,
The results are completely stable, from 5 to 5000 requests, and with
concurrency from 1 to 10ish. I'm running on linux, haven't had any
issues with ab before. I actually initially noticed the issue using
jmeter.
The timing is stable enough that it feels like a timeout or artif
Hi Jeff,
30 requests are not a lot. Are these results stable?
When I tried to repeat your results, I started the server
with your configuration:
/usr/local/ns/bin/nsd -u nsadmin -t ~/scripts/aol/jeff-conf.tcl -f
When running "ab" without -k" and 1000 requests:
ab -n 1000 -c 1 http://lo
