Comment by gwbas1c

> Proper usage means disabling Nagle at the socket level but managing your own buffering in user-space.

Honestly, if you're writing a (cough) typical webservice that just serializes an object to JSON, you've pretty much done that. Nagle just slows that situation down, and TCP_NODELAY should always be enabled in that situation. (Granted, if you're using newer HTTP (3? SPDY?) you probably aren't even on TCP and don't even need to bother.)

It's only when sending large payloads that you might have to think about buffering.