From: "Stephen C. Tweedie" <sct@redhat.com>
To: Neil Conway <nconway.list@ukaea.org.uk>
Cc: Rik van Riel <H.H.vanRiel@phys.uu.nl>,
Linux MM <linux-mm@kvack.org>,
Jean-Michel.Vansteene@bull.net,
"linux-kernel@vger.rutgers.edu" <linux-kernel@vger.rutgers.edu>
Subject: Re: SWAP: Linux far behind Solaris or I missed something (fwd)
Date: Fri, 4 Dec 1998 14:49:11 GMT [thread overview]
Message-ID: <199812041449.OAA04573@dax.scot.redhat.com> (raw)
In-Reply-To: <98Dec4.104023gmt.66305@gateway.ukaea.org.uk>
Hi,
On Fri, 4 Dec 1998 10:41:15 +0000, Neil Conway
<nconway.list@ukaea.org.uk> said:
>> (although the 2.1.130+my patch seems to work very well
>> with extremely high swap throughput)
> Since the poster didn't say otherwise, perhaps this test was performed
> with buffermem/pagecache.min_percent set to their default values, which
> IIRC add up to 13% of physical RAM (in fact that's PHYSICAL ram, not 13%
> of available RAM). So take a 1024MB machine, with (say) roughly 16MB
> used by the kernel and kernel-data. Then subtract 0.13*1024 (133MB !!)
> and you're left with a paltry 875MB or so. (This assumes that the
> poster had modified his kernel to handle the full 1024MB btw).
I know. That's why relying on fixed margins to ensure good
performance is wrong: the system really ought to be self-tuning.
We may yet get it right for 2.2: there are people working on this.
--Stephen
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next prev parent reply other threads:[~1998-12-04 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-03 12:03 Rik van Riel
1998-12-04 10:41 ` Neil Conway
1998-12-04 14:49 ` Stephen C. Tweedie [this message]
1998-12-04 15:23 ` Rik van Riel
1998-12-05 7:51 ` MOLNAR Ingo
1998-12-04 12:05 ` Stephen C. Tweedie
[not found] ` <3667E533.ADFBFDBB@bull.net>
1998-12-04 14:47 ` Stephen C. Tweedie
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=199812041449.OAA04573@dax.scot.redhat.com \
--to=sct@redhat.com \
--cc=H.H.vanRiel@phys.uu.nl \
--cc=Jean-Michel.Vansteene@bull.net \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=nconway.list@ukaea.org.uk \
/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