Hacker News new | ask | show | jobs
by zamadatix 1118 days ago
> 60ms @ 1gbit (120 MiB) -> 7.2 MiB TCP buffer size required for bandwidth saturation. That’s more than the max buffer size a run-of-the-mill modern OS gives you by default

Windows was quite happy to give me a 40,960 * 512 = 20,971,520 byte TCP window for a single stream speed test from mid US to London, run via Chrome. Linux is the only one I've noticed with stingy max buffers. I never really understood why user-focused distros like to keep the max so limited when there are plenty of resources.
1 comments
klabb3 1118 days ago
That’s great to hear! Thanks for the data point, hope this is more representative. I’ve encountered Windows (10) instances in the wild with auto-tuning turned off (64k max).

> I never really understood why user-focused distros like to keep the max so limited when there are plenty of resources.

Yeah, agreed. That is way too conservative, especially for an issue which most people can’t easily triage.

link
zamadatix 1118 days ago
You can definitely turn it off in Windows, should you want to for some reason, but scaling windows up to 1G are definitely the default since Windows 2000 https://web.archive.org/web/20130613080612/http://www.micros...
link