Re: Ongoing 2.4 VM suckage

["Jakob Østergaard" <jakob@unthought.net>]

On Thu, Aug 02, 2001 at 02:11:21PM -0700, Jeffrey W. Baker wrote:
> 
> 
> On Thu, 2 Aug 2001, Richard B. Johnson wrote:
> 
> > Well I don't have any such problems here. I wrote this script
> > from your instructions. I don't know if you REALLY wanted all
> > the file content to go out to the screen, but I wrote it explicitly.
> 
> [snip]
> 
> > Script started on Thu Aug  2 16:50:47 2001
> > # ps -laxw | grep pause
> >    140     0    16     1  -1 -20    712    40 pause       S < ?   0:00 (bdflush) te
> >      0     0  7433     1   9   0 321056 137808 pause       S    1  0:02 /tmp/try
> >      0     0  7631  7626  19   0    844   240             R   p0  0:00 grep pause
> > # cat /proc/meminfo
> >         total:    used:    free:  shared: buffers:  cached:
> > Mem:  328048640 326234112  1814528        0  4255744 173219840
> > Swap: 1069268992 189992960 879276032
>                              ^^^^^^^^^
> You still have almost 1GB of swap left.  I mean use all the memory in your
> box, RAM + swap.
> 
> As I said, I expect degraded performance but not a complete meltdown.

What ?

You fill up mem and you fill up swap, and you complain the box is acting funny ??

This is a clear case of "Doctor it hurts when I ..."  -  Don't do it !

I'm interested in hearing how you would accomplish graceful performance
degradation in a situation where you have used up any possible resource on the
machine.  Transparent process back-tracking ?   What ?

-- 
................................................................
:   jakob@unthought.net   : And I see the elder races,         :
:.........................: putrid forms of man                :
:   Jakob Østergaard      : See him rise and claim the earth,  :
:        OZ9ABN           : his downfall is at hand.           :
:.........................:............{Konkhra}...............: