low-memory testing

[James Cameron]

On Sun, Oct 28, 2007 at 11:23:13PM -0400, Albert Cahalan wrote:
> Current OOM score: /proc/*/oom_score
> Adjustment: /proc/*/oom_adj
> 
> Adjustments run from -17 (never kill) to 15.
> 
> Starting each activity with oom_adj=15 would
> be a good start.

I've just tried something like that, and it worked nearly as well as I
hoped.

Build 623, on B4.  Started a Sugar Console, hid it again, started
Browse, then in an SSH session I set the Browse oom_adj to 15, left
everything else as it was, and ran a fork-bomb consisting of a bash
script that invokes itself.

http://dev.laptop.org/~quozl/2007-10-30-os-623-b4-oom-dmesg.txt

This shows the first to be killed was Browse, which was my intention.

It did take a fair while for it to happen though, during which the
system was very unresponsive.

-- 
James Cameron    mailto:quozl at us.netrek.org     http://quozl.netrek.org/