4 ms·
Linux's OOM killer always seems to run too late (once it's already locked up meaning it takes like half an hour for it to free up the memory. It's been like thi
by charcircuit 5y ago
Linux's OOM killer always seems to run too late (once it's already locked up meaning it takes like half an hour for it to free up the memory. It's been like this for years, so I hope someone eventually fixes it.
- themodelplumber 5y agoFor sure, it seems like a really strange problem. However I've noticed it's not consistently an issue across various Linux systems I run here. So I wonder if this variance due to different configurations (or whatever it is) has led to a lack of a louder "please fix ASAP" sentiment.
- charcircuit 5y agoI wonder if they could implemented some sort of logging where people could submit cases where it's failed for them.
- _3u10 5y agoAdd some swap to your system, drastically reduces OOM killer frequency.
- charcircuit 5y agoI'm sure this would help, but I have 64GB of RAM. Linux should be able to figure out how to save some of that massive amount of memory so that it can save itself.
- rnhmjoj 5y agoWhen the system runs out of memory the OOM killer is actually invoked right away. The problem is that systems with modern fast storage can run for hours with little to no memory left without really going OOM. If you're interested in this, I've explained how this happens in this thread: https://news.ycombinator.com/item?id=28771003 https://news.ycombinator.com/item?id=28771003
- charcircuit 5y agoI understand this, but I want to point out while it's locked up thrashing you can't use sysrq to invoke the OOM so you have to wait anyways. By too late, I meant that manually invoking (sysrq) the OOM before it starts thrashing prevents it from totally locking up.
- rnhmjoj 5y ago> I understand this, but I want to point out while it's locked up thrashing you can't use sysrq to invoke the OOM so you have to wait anyways. Invoking the OOM killer with sysrq has always worked for me, strange.