4 ms·
Also, for small packets, disabling consolidation means adding LOTS of packet overhead. You're not sending 1 million * 50 bytes of data, you're sending 1 million
by drpixie 4y ago
Also, for small packets, disabling consolidation means adding LOTS of packet overhead. You're not sending 1 million * 50 bytes of data, you're sending 1 million * (50 bytes of data + about 80 bytes of TCP+ethernet header).
Disabling Nagle makes sense for tiny request/replys (like RPC calls) but it's counterproductive for bulk transfers.
I'm not the only one who don't like the thought of a standard library quietly changing standard system behaviour ... so know I have to know the standard routines and their behaviour AND I have to know which platforms/libraries silently reverse things :(
- boring_twenties 4y agoBulk transfer applications should just use larger buffers
- josefx 4y agoWouldn't that still end up with sub optimal network messages unless those large buffers are an exact multiple of the MTU on the network?
- boring_twenties 4y agoHm, I'm not 100% sure about this. If your first buffer is big enough, your next write should be issued before the OS has managed to write it all.