Re: Ongoing 2.4 VM suckage

Anders Peter Fugmann
2001-08-03T12:07:34Z

Hi.

While reading this thread, there is something that I do not quite
understand, and I hope that some of you could please explain it to me.

Why is the machine going dead (soft-deadlock as someone called it)? If
there is not enough avaiable memory for a process in running state to
actually run, other processes would be swapped out right, but this
"simple" operation should not bring the machine down should it.

If the reason for the machine going bad is because when the running
process eventually (or even before) gets all it memory to actually run,
it is rescheduled, I see a simple solution.

Stop rescheduling too often when memory is low. Rescheduling is very
memory demanding (in terms of swapping and stuff), and that is not
helping the situation.

Any thought on this, or am I compleatly mistaken?

Regards
Anders Fugmann