3 ms·
> just need better hardware. That's .. yeah, that's completely false. I can think of dozens of things that are not right out of the box on any distro, on any h
by jeffbee 3y ago
> just need better hardware.
That's .. yeah, that's completely false. I can think of dozens of things that are not right out of the box on any distro, on any hardware, in common practice. For example suppose you roll out Ubuntu on an EC2 instance, say a c6i.16xlarge, a 32C/64T, single-socket x86 server with a Nitro ENA. Where are the netrx interrupts delivered? Is RSS on/working? RPS, XPS? Interrupt coalescing? The distro can't make optimal choices for all use cases, but what they ship by default is a config that's not optimal for any use case. Literally nobody would consciously choose the defaults after thinking it over.
- n3storm 3y agothat is the free/open bsd (from what I know) thinking path and I love there are linux people that think on that terms too. not every year is the Linux on the Desktop year! :D
- bravetraveler 3y agoMost common example I can think of is 'net.core.somaxconn'. The default limit out of the box is laughably small. Has been for decades at this point.
- Jach 3y agoIs 4096 still too small over 128? https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19f92a030ca6d772ab44b22ee6a01378a8cb32d4 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...
- jeffbee 3y agoAccording to that message, they lifted it to 4096 8 years ago, presumably for reasons. Have your systems got any bigger or faster since 2015?
- bravetraveler 3y agoNope, that's pretty decent ... this still hasn't made it to the distributions we're using, though. More specifically: the kernel releases. There's a lot in service pre 5.4. Hanging on by a thread. Relief is near.