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.
We should probably change the default for "nodelay" on nssock and
nsssl from "false" to "true". It seems, that e.g. mozilla has done this
~8 years ago.
all the best
-g
PS: setting minthreads is limited to the current value of maxthreads.
so, when setting only minthreads to a value of 20 (as in your example)
the effective value is 10 (the default for maxthreads). So, probably
we should align the value of maxthreads when setting the value
of minthreads above maxthreads, and vice versa when setting
maxthreads to a value lower than minthreads.
ns_section "ns/servers"
ns_param default Naviserver
ns_section "ns/server/default"
ns_param maxthreads 20
ns_param minthreads 20
ns_section "ns/server/default/modules"
ns_param nssock nssock.so
ns_param nslog nslog.so
ns_section "ns/server/default/module/nssock"
ns_param port 8080
ns_param nodelay true
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, which
happens on linux, but not on macOS.
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
