3 ms·
I wouldn't worry too much about that claim. It seems like a poorly remembered claim about about a very old version. I'm sure somebody has the battlescars and co
by toast0 7y ago
I wouldn't worry too much about that claim. It seems like a poorly remembered claim about about a very old version. I'm sure somebody has the battlescars and could tell you what it was exactly.
My guesses would be a memory leak somewhere, some yucky disk controller bug I didn't run into, or possibly the TCP LAST_ACK state accumulation https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=25986 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=25986
This has since been fixed, although it did take an annoyingly long time; but before it was fixed, you could address it by tuning socket buffers to be smaller --- it seemed to be less likely for clients to disappear with unacked data, but also, when they did, it wasn't as noticeable.
Most things are tuned pretty well by autotuning these days though. If your work is more I/O limited than CPU limited though, tuning is more likely to be useful.