oom-killer with 27G free swap and overcommit_memory=2
Quoted 8 lines · Patrick J. LoPresti
My system is a SunFire x4100 (
x86_64) with 16G of RAM and 32G of swap in a single partition. I have an application which consumes a lot of memory, and after a few hours the oom-killer kills it.This would not be surprising, except a) the machine still has 27G of free swap at the time; and b) it happens even when I set vm.overcommit_memory=2 (with overcommit_ratio=50). It is time-consuming to reproduce, but consistent.
:
:
Quoted 2 lines
2) Is there any sysctl setting that might "avoid" this problem? Or a way to change my application to avoid it?
Try setting the overcommit_ratio=0.
Thanks!
--
Al