> [...I] asked on Slack if that 40ms value was familiar to anyone. Nothing.<p>In the future, you should use this as an excuse to read more HN at work ;): <a href="https://news.ycombinator.com/item?id=24785405" rel="nofollow">https://news.ycombinator.com/item?id=24785405</a>
As soon as he mentioned a fixed 40ms delay, my first guess was some obscure TCP configuration.<p>TCP is one of those ubiquitous things everyone takes for granted, but is more complex than most people realize.
Same old bug, same old blog post repost: <a href="http://forwardscattering.org/post/3" rel="nofollow">http://forwardscattering.org/post/3</a> "Sockets should have a flushHint() API call"
I'm not a network guy and even I know about nagle. Then again I read a lot.<p>So the author and a colleague didn't know - 2 people who worked on a networking utility and had to spend days digging into it. The cost of reading books is high but the ROI is higher. Maybe they got unlucky but being a dev needs considerable knowledge but companies want their full stack devs cheap.