News for hackers. Stuff that matters.
Re:Golang is evil on shitty networks by drpixie on Friday December 30, 2022 @12:17AM (#34182081)
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 :(

Re:Golang is evil on shitty networks by boring_twenties on Friday December 30, 2022 @01:42AM (#34182541)
Bulk transfer applications should just use larger buffers
Re:Golang is evil on shitty networks by josefx on Friday December 30, 2022 @01:55AM (#34182606)
Wouldn't that still end up with sub optimal network messages unless those large buffers are an exact multiple of the MTU on the network?
Re:Golang is evil on shitty networks by boring_twenties on Tuesday January 03, 2023 @09:49AM (#34232007)
Hm, 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.