| |||||||||||||
Blocking on allocation failure - WTF?Blocking on allocation failure - WTF?Posted Mar 11, 2011 1:05 UTC (Fri) by dgm (subscriber, #49227)In reply to: Blocking on allocation failure - WTF? by dgm Parent article: Delaying the OOM killer
I hate to reply to myself, but I just got it wrong. Overcommit in Ubuntu uses the kernel default, that is, do overcommit. As an experiment I turned it off (setting /proc/sys/vm/overcommit_memory to 2) and after that I couldn't start a new instance of chromium in a not very loaded system (a couple of terminals and Nautilus).
So apparently it's not only useful but critical.
(Log in to post comments)
Blocking on allocation failure - WTF? Posted Mar 11, 2011 7:19 UTC (Fri) by Darkmere (subscriber, #53695) [Link]
Blame chrome there. They allocate a fair chunk of RAM to start with for their javascript memorypool. ( That wants to be continuous, iirc)
Basically, Chrome is designed around Overcommit. As are a few other apps.
Blocking on allocation failure - WTF? Posted Mar 11, 2011 23:57 UTC (Fri) by giraffedata (subscriber, #1954) [Link] So apparently it's not only useful but critical. Isn't the problem just that you adjusted /proc/sys/vm/overcommit_memory without making the corresponding adjustment in the amount of swap space?
|
|||||||||||||