Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Stuff like this just proves that a large part of this job is just remembering a bunch of weird data points and knowing when to match this story to that problem.

I've hit Nagle far in the past, and reading the title I thought 'well that can't be about Nagle because that was a 200ms delay'

Looks like someone tuned it down to 40ms but didn't dare removing it. It would be interesting to know how they came to that choice



I thought the delay was set in the 'delayed ack' setting?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: