Re: [PATCH] [2.4.17/18pre] VM and swap - it's really unusable

["M.H.VanLeeuwen" <vanl@megsinet.net>]

Stephan von Krawczynski wrote:
> 
> On Mon, 31 Dec 2001 11:14:04 -0600
> "M.H.VanLeeuwen" <vanl@megsinet.net> wrote:
> 
> > [...]
> > vmscan patch:
> >
> > a. instead of calling swap_out as soon as max_mapped is reached, continue to
> try>    to free pages.  this reduces the number of times we hit
> try_to_free_pages() and>    swap_out().
> 
> I experimented with this some time ago, but found out it hit performance and
> (to my own surprise) did not do any good at all. Have you tried this
> stand-alone/on top of the rest to view its results?


No benchmarks specifically to show changes yet.  Hmmm, I found quite the opposite from
an interactive feeling on SMP and I was happy not to have a kernel killing processes
out of the blue when it started hitting the upper limits of VM.  Especially when there
was still plenty of cache to be evicted (the original reason for the OOM tamer).

Yes, your performance loss may be from having less cache overall since the kernel is
swapping out less. OTOH we tend to not hit shrink_[di]cache_memory much less with this
change.

I'll try to time some kernel compiles with the vmscan patch...
compile times and amount of swap used afterwards, from a cold start and subsequent
compile, etc.

Andreas Hartmann generated a comparison of many kernel VM's including Andrea's and Rick's
and the last AC patch.  I'll send it to you separately since it is rather large and
everyone Cc'd has already seen it.

As was pointed out earlier it sure will be nice once we have some cache stats...

Willing to give this one a try to see if it is still a performance hit for you? 
VM has probably change since "some time ago". ;)


Martin