Re: Ongoing 2.4 VM suckage

[Jeffrey W. Baker]

On Thu, 2 Aug 2001, Rik van Riel wrote:

> If you have a proposal on what to do when both ram
> and swap fill up and you need more memory, please
> let me know.
>
> Until then, we'll kill processes when we exhaust
> both memory and swap ;)

I'm telling you that's not what happens.  When memory pressure gets really
high, the kernel takes all the CPU time and the box is completely useless.
Maybe the VM sorts itself out but after five minutes of barely responding,
I usually just power cycle the damn thing.  As I said, this isn't a
classic thrash because the swap disks only blip perhaps once every ten
seconds!

You don't have to go to extremes to observe this behavior.  Yesterday, I
had one box where kswapd used 100% of one CPU for 70 minutes straight,
while user process all ran on the other CPU.  All RAM and half swap was
used, and I/O was heavy.  The machine had been up for 14 days.  I just
don't understand why kswapd needs to run and run and run and run and run
...

I'm very familiar with what should happen on a Unix box when user
processes get huge.  On my FreeBSD and Solaris machines, everything goes
to shit for a few minutes and then it comes back.  Linux used to work that
way too, but I can't count on the comeback in 2.4.

-jwb