[Gllug] Forcing CPU and Mem limits on a process

[Richard Huxton]

Nix wrote:
> On Fri, 11 Feb 2005, Jack Richards said:
> 
>>overcommit mem is a great spead improver, however don't use it if you don't 
>>have enough ram, otherwise the kernel OOM killer kicks in and you start 
>>getting unexpected results  
> 
> Er, what results would you expect if you tried to actually use more
> mem+swap than you had? I'm having trouble thinking of non-surprising
> semantics here...

I think the problem is not so much that the kernel goes around killing 
processes to reclaim memory. Rather, AFAIK you can't tell which of your 
processes will die ahead of time. In particular, I believe a large 
database process can look very attractive as a target when reclaiming 
memory, whereas you'd probably want almost everything else killed first 
if possible.

--
   Richard Huxton
   Archonet Ltd
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug