linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: Joseph Bueno <joseph.bueno@trader.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: VM balancing problems under 2.4.2-ac1
Date: Sat, 24 Feb 2001 09:37:49 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.31.0102240935590.8568-100000@localhost.localdomain> (raw)
In-Reply-To: <3A978DF8.FB1890E@trader.com>

On Sat, 24 Feb 2001, Joseph Bueno wrote:
> Rik van Riel a écrit :
> > On 23 Feb 2001, Adam Sampson wrote:
> >
> > > The VM balancing updates in the recent ac kernels seem to have caused
> > > some interesting performance problems on my desktop machine. I've got
> > > 160Mb of RAM, and 2.4.2-ac1 appears to be using excessively large
> > > amounts of it for buffers and cache while pushing stuff out to
> > > swap. This means that Mozilla, for instance, runs significantly worse
> > > than under 2.4.0, since bits of it are being swapped in and out.
> >
> > This is a known problem which I'll fix as soon as I have a
> > solution.
> >
> > The problem is that we still have no good way to balance
> > how much memory we take from the cache and how much memory
> > we take from processes.

> I understand that auto-balancing code that deals with all
> situations is very hard to design; so let me share my experience
> on other Unix systems (from a user/administrator point of view):
>
> I have used Unix systems (mainly HPUX) for several years as personal
> workstations or servers and buffer cache usage were very differents:
>
> On workstations, you are mainly looking for fast interactive response
> time and  you want to dedicate as much memory as possible to running
> processes so limiting buffer cache to 10% of physical memory (these
> workstations had typically 32 - 64 Mb of RAM) was good.

"Unfortunately" the cache also contains _process memory_ in
Linux. Limiting the cache to 10% also means limiting the
code size of all your processes to something smaller than
that.

Also, read-in swap pages are in the so-called swap cache,
which is also part of the page cache.

This means that simple limits on cache size probably won't do
much good on Linux.

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://www.conectiva.com/	http://distro.conectiva.com.br/


  reply	other threads:[~2001-02-24 14:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-23 20:00 VM balancing problems under 2.4.2-ac1 Adam Sampson
2001-02-24  2:22 ` Rik van Riel
2001-02-24 10:33   ` Joseph Bueno
2001-02-24 14:37     ` Rik van Riel [this message]
2001-02-26 16:33   ` Mike Galbraith
2001-03-03  0:03   ` Adrian Bunk
2001-03-04 17:26     ` Ingo Oeser
2001-03-05  7:05       ` Mike Galbraith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.31.0102240935590.8568-100000@localhost.localdomain \
    --to=riel@conectiva.com.br \
    --cc=joseph.bueno@trader.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).