3 ms·
> all Linux distributions are tuned for nothing in particular. Which is good, because often tuning means making trade-offs. A lot of those things like polling
by rdtsc 11y ago
> all Linux distributions are tuned for nothing in particular.
Which is good, because often tuning means making trade-offs. A lot of those things like polling and interrupt shuffling have side effects and might for example negatively impact other scenarios -- presumably not everyone out there is running single client-server ping-pong with small UDP packets.
Yes a lot of parameters have retained default values from back in the day when system characteristics were different. Switching defaults drastically might break existing code that relied on them. Perhaps those are better updated during major distro version upgrades (RHEL 6->7 for ex).
In general though, I would say Linux is tuned for average throughput not latency. Sometimes they go hand in hand, sometimes they don't. Over the years there have been patches and forks related to operating on low latency environments (stock trading, media processing, hardware control, graphics in desktop environment). Those range from parameters tweaks in /proc to kernel patches, to almost full kernel bypass via things like DPDK for Ethernet for example.
- thrownaway2424 11y agoSure, they are all tradeoffs of some kind or another. It's crazy to think that one person deploying a linux box on AWS would be aware of them all, though. For example what is the default file-max on Ubuntu? Why?
- rdtsc 11y agoWell you have different use cases and you have a large panel of nobs and switches you can adjust. You need someone who knows what the knobs do and what effect they have. So perhaps there is a use case for wizard like configuration tool for intermediate users. It can ask you questions like -- how many clients do you have? How many concurrent connections. Would you rather have higher average throughput (say for downloading files) or lower packet latency (say for audio processing). Would you rather use your memory for a file cache for for your application data. And so on. Next step up -- a self tuning system. It monitors your usage pattern then decides what settings to use. Monitors again, and adjusts a bit and so on.
- gshx 11y agoI've always been somewhat wary of the self tuning systems. The challenge is that the runtime profile of a well-utilized machine is not always predictable especially if it is multi-tenant and/or running a mixture of different workloads in a container like abstraction. I think a level higher is easier to manage and understand, so, we're dealing with and managing multiple machines or multiple containers of vm's as processing units. As a whole, that seems more manageable as a self tuning system.
- rdtsc 11y agoTuning profiles could be suggested and an human would apply them. But yeah, that was more of a pie in the sky idea.