From: Joel Becker <Joel.Becker@oracle.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Autotune swappiness01
Date: Mon, 26 Jul 2004 13:29:46 -0700 [thread overview]
Message-ID: <20040726202946.GD26075@ca-server1.us.oracle.com> (raw)
In-Reply-To: <cone.1090802581.972906.20693.502@pc.kolivas.org>
On Mon, Jul 26, 2004 at 10:43:01AM +1000, Con Kolivas wrote:
> Low memory boxes and ones that are heavily laden with applications find
> that ends up making things slow down trying to keep all applications in
> physical ram.
Lowish memory boxes with plain desktop loads find that the default
of '60' is a terrible one (I'm speaking of 1GHz-ish machines with 256MB
(like mine) or 512MB (like a guy next to me)). Every person I know who
installs 2.6 complains about how it feels slow and choppy. I tell them
"The first thing I do after installing 2.6 is set swappiness to '20'."
Sure enough, they set swappiness to 20 and their box starts behaving
like a properly tuned one.
I don't know what workload the default of '60' is for, but for
the (128MB < x < 1GB) of RAM case, it sucks (and I've seen the same
behavior on a 300MHz 196MB box).
Joel
--
"Maybe the time has drawn the faces I recall.
But things in this life change very slowly,
If they ever change at all."
Joel Becker
Senior Member of Technical Staff
Oracle Corporation
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2004-07-26 20:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 0:25 [PATCH][2.6.8-rc1-mm1] Autotune swappiness01 Con Kolivas
2004-07-26 0:36 ` Andrew Morton
2004-07-26 0:43 ` Con Kolivas
2004-07-26 0:48 ` Andrew Morton
2004-07-26 1:01 ` Con Kolivas
2004-07-26 1:09 ` Con Kolivas
2004-07-26 8:52 ` R. J. Wysocki
2004-07-26 9:31 ` Con Kolivas
2004-07-26 10:34 ` R. J. Wysocki
2004-07-26 10:29 ` Con Kolivas
2004-07-26 10:54 ` R. J. Wysocki
2004-07-26 11:03 ` Con Kolivas
2004-07-26 11:13 ` Nick Piggin
2004-07-26 11:17 ` Con Kolivas
2004-07-26 11:47 ` Nick Piggin
2004-07-26 13:53 ` R. J. Wysocki
2004-07-26 18:45 ` Adam Kropelin
2004-07-26 18:53 ` R. J. Wysocki
2004-07-26 17:55 ` Gerrit Huizenga
2004-07-26 20:29 ` Joel Becker [this message]
2004-07-26 20:42 ` Andrew Morton
2004-07-26 22:58 ` Con Kolivas
2004-07-27 0:52 ` Clemens Schwaighofer
2004-07-27 1:09 ` Andrew Morton
2004-07-27 1:17 ` Clemens Schwaighofer
2004-07-27 2:03 ` Tim Connors
2004-07-27 2:43 ` Con Kolivas
2004-07-27 3:02 ` Tim Connors
2004-07-27 3:43 ` Clemens Schwaighofer
2004-07-27 3:47 ` Joel Becker
2004-07-27 15:32 ` William Lee Irwin III
2004-07-27 3:41 ` Clemens Schwaighofer
-- strict thread matches above, loose matches on Subject: below --
2004-07-26 14:52 Martin Knoblauch
2004-07-26 21:29 DaMouse
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=20040726202946.GD26075@ca-server1.us.oracle.com \
--to=joel.becker@oracle.com \
--cc=akpm@osdl.org \
--cc=kernel@kolivas.org \
--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