42 ms·
Oh that’s a known problem. There are many kernel patches floating around that fix it by triggering the OOM killer when the system is thrashing. Here’s one based
by NavinF 5y ago
Oh that’s a known problem. There are many kernel patches floating around that fix it by triggering the OOM killer when the system is thrashing. Here’s one based on ChromeOS’s solution: https://github.com/hakavlad/le9-patch https://github.com/hakavlad/le9-patch
I’ve never had this specific problem back when I was daily driving desktop Linux, but I did run into 1000 other ones that needed bandaid solutions just like this. It’s death of a thousand cuts: https://news.ycombinator.com/item?id=28490753 https://news.ycombinator.com/item?id=28490753
I see that nothing’s changed in the last couple of years.
- themodelplumber 5y agoJust curious, do you believe there's an OS out there right now without this thousand cuts problem?
- NavinF 5y agoOh yes, 4 of them. Windows, macos, android, and ios only have a handful of cuts in my experience. I'm not saying that's entirely linux's fault or anything. It's just that desktop linux has a market share of around 1% (depending on your source) and even that's fragmented across several distros. Hardly anyone tests their software or hardware on linux, let alone the distro you happen to use. Some of the problems I listed used to be an issue on other OSs. For example Android used to have ridiculous audio latency on the order of 400ms, but a few years ago Google got their shit together and fixed that: https://source.android.com/devices/audio/latency/measurements#examples https://source.android.com/devices/audio/latency/measurement... The same can't be said for desktop linux. I don't think any of the distros even have a device farm for end-to-end latency measurements. The other 4 OSs have extensive testing and the devs care about user metrics.