Re: Ongoing 2.4 VM suckage

Anders Peter Fugmann
2001-08-03T22:00:57Z

See you point very well.

So I guess the problem is, that we want to keep the CPU busy while
fetching the data the program wants.

This would mean, that having two processes that activly uses more than
half of the memory would compete against each other and noone would
never win, resulting in very bad performance - actually I would rather
want the CPU to "twiddle thumbs" while waiting for the data, than a
system that will halt for minutes (but that is very sub-optimal).

A solution may be to make sure that a program suspended by the VM gets
higher priority than other processes, and thus provoking the VM-layer to
fetch the data for the process more often than others. This would not
give a fair system, but it would behave better under memory pressure.

Regards
Anders Fugmann

Rik van Riel wrote:
> On Fri, 3 Aug 2001, Anders Peter Fugmann wrote:
>
>
>>I dont know task states are defined, but by 'running' I mean that it
>>is not stopped by the VM, when the VM needs to fetch memory for the
>>process.
>>
>
> What do you propose the program does when it doesn't have
> its data ? Better give up the CPU for somebody else than
> twiddle your thumbs while you don't have the data you want.
>
> regards,
>
> Rik
> --
> Virtual memory is like a game you can't win;
> However, without VM there's truly nothing to lose...
>
> http://www.surriel.com/ http://distro.conectiva.com/
>
> Send all your spam to aardvark@nl.linux.org (spam digging piggy)
>
>