Everything is a Freaking DNS problem - oomkiller http://127.0.0.1:8080/blog/taxonomy/term/777/0 en Let's get rid of the OOM Killer http://127.0.0.1:8080/blog/node/590 <p><a href="http://weblog.verwilst.be/2008/02/07/avoiding-ooms-with-mem_notify/" rel="nofollow">Bort</a> pointed us to a <a href="http://www.linuxworld.com/news/2008/020508-kernel.html" rel="nofollow">new interesting feature in the linux kernel. </a></p> <p>This is really good news, we'll be able to get input from the kernel on the fact that it is about to start doing things we don't like. </p> <p>Looking at a random machine<br /> <div class="geshifilter"><pre class="text geshifilter-text" style="font-family:monospace;"><ol><li style="font-family: monospace; font-weight: normal;"><div style="font-family: monospace; font-weight: normal; font-style: normal"> total used free shared buffers cached</div></li><li style="font-family: monospace; font-weight: normal;"><div style="font-family: monospace; font-weight: normal; font-style: normal">Mem: 2017 1128 889 0 53 443</div></li></ol></pre></div><br /> that's 443 Mb that an application that is aware of this new feature free its own share of.</p> <p>It's not only Java applications that should be polling this device frequently ..<br /> firefox, clock-applet, liferea, gnome-terminal, VirtualBox and evolution also might want to look at it .</p> <p>Thank you for cleaning up your mess ! :)</p> http://127.0.0.1:8080/blog/node/590#comments memory management oomkiller Thu, 07 Feb 2008 20:43:13 +0000 Kris Buytaert 590 at http://127.0.0.1:8080/blog