From: Mike Castle <dalgoda@ix.netcom.com>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Recommended swap for 2.4.x.
Date: Mon, 29 Jan 2001 15:45:22 -0800 [thread overview]
Message-ID: <20010129154521.J17481@thune.yy.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10101291348330.9791-100000@penguin.transmeta.com> <Pine.LNX.4.10.10101291452120.31258-100000@clueserver.org> <20010129152335.H11411@draco.foogod.com>
In-Reply-To: <20010129152335.H11411@draco.foogod.com>; from alex@foogod.com on Mon, Jan 29, 2001 at 03:23:35PM -0800
On Mon, Jan 29, 2001 at 03:23:35PM -0800, alex@foogod.com wrote:
> On Mon, Jan 29, 2001 at 02:57:44PM -0800, Alan Olsen wrote:
> > The standard rule is usually memory x 2. (But that is more a Solaris
> > superstition than anything else.)
>
> This always struck me as the most stupid rule of thumb I'd ever heard of.
> With this metric, systems which precisely need swap the most (low-RAM systems)
> get the least of it, and those that need it the least (those with gigs of RAM)
> get tons of swap they don't need. I don't know how this keeps perpetuating,
> as it should be plainly brain damaged to anybody who thinks about it for a
> couple of seconds, but somehow it does.
Because it used to be necessary.
Early VM systems *required* at least one page of swap for every page of
physical ram. In theory, the entire contents of physical ram would be
copied at any time onto swap, and whenever it was necessary to free up a
page to bring in a new one, it would already be on backing store and could
easily be freed up.
This was prior to things like being able to page in binaries from file
systems on demand, so your programs had to be swapped back out as well.
So, basically, your totally usable paging area was the sum of swap space.
Not the sum of swap space + physical memory.
Now, granted, this is no longer the case for most (all?) VM based systems,
the rule of thumb has such strong momentum behind it that it's difficult to
stop.
Now, personally, I tend to throw on a few meg of swap onto each disk and
stripe swap across them for performance. If I find I ever run out of
memory under normal use, I'll up it. But I've never had that happen. Swap
space depends on how you use it. Set up some stuff, and monitor with free
every once in a while. If you never hit swap, then reduce it or eliminate
it. If you are constantly running over 1/3 of it or so, might consider
upping it a little bit.
mrc
--
Mike Castle Life is like a clock: You can work constantly
dalgoda@ix.netcom.com and be right all the time, or not work at all
www.netcom.com/~dalgoda/ and be right at least twice a day. -- mrc
We are all of us living in the shadow of Manhattan. -- Watchmen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-29 23:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 21:51 2.4.0-test12: SiS pirq handling Linus Torvalds
2001-01-29 22:06 ` Sven Koch
2001-01-29 22:57 ` Recommended swap for 2.4.x Alan Olsen
2001-01-29 23:04 ` Linus Torvalds
2001-01-29 23:23 ` alex
2001-01-29 23:45 ` Mike Castle [this message]
2001-01-29 23:49 ` William T Wilson
2001-01-30 0:24 ` Kevin Krieser
2001-01-30 5:20 ` Jeff Chua
2001-01-30 19:21 ` James H. Cloos Jr.
2001-01-30 1:20 ` idalton
2001-01-30 11:48 ` Rik van Riel
2001-01-30 18:10 ` alex
2001-01-30 18:22 ` Rik van Riel
2001-01-30 18:40 ` Matthew Kirkwood
2001-01-30 18:43 ` Rik van Riel
2001-01-31 19:59 ` Russell King
2001-01-30 19:13 ` alex
2001-01-30 19:28 ` Rik van Riel
2001-02-02 13:51 ` Pavel Machek
2001-02-02 22:58 ` Alan Olsen
2001-02-02 20:27 ` Jonathan Morton
2001-01-29 23:17 ` 2.4.0-test12: SiS pirq handling Aaron Tiensivu
2001-01-29 23:44 ` Linus Torvalds
2001-01-30 0:34 ` Aaron Tiensivu
2001-01-31 10:19 ` Martin Diehl
2001-01-30 1:38 ` Adam Huffman
2001-01-31 10:21 ` [PATCH] minor ne2k-pci irq fix Martin Diehl
2001-01-31 12:11 ` davej
2001-02-01 0:01 ` Martin Diehl
2001-02-01 15:06 ` Jeff Garzik
2001-02-02 16:49 ` Martin Diehl
2001-02-02 17:05 ` Jeff Garzik
2001-02-03 20:20 ` Linus Torvalds
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=20010129154521.J17481@thune.yy.com \
--to=dalgoda@ix.netcom.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