public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: LA Walsh <law@sgi.com>
Cc: Rogier Wolff <R.E.Wolff@BitWizard.nl>,
	Xavier Bestel <xavier.bestel@free.fr>,
	Goswin Brederlow <goswin.brederlow@student.uni-tuebingen.de>,
	William T Wilson <fluffy@snurgle.org>,
	Matt_Domsch@Dell.com, linux-kernel@vger.kernel.org
Subject: Re: 2.4 and 2GB swap partition limit
Date: Sat, 28 Apr 2001 09:47:20 +0200 (MEST)	[thread overview]
Message-ID: <200104280747.JAA03559@cave.bitwizard.nl> (raw)
In-Reply-To: <3AE9DC22.597D94F5@sgi.com> from LA Walsh at "Apr 27, 2001 01:52:50 pm"

LA Walsh wrote:
> Rogier Wolff wrote:
> 
> > > > On Linux any swap adds to the memory pool, so 1xRAM would be
> > > > equivalent to 2xRAM with the old old OS's.
> > >
> > > no more true AFAIK
> >
> > I've always been trying to convice people that 2x RAM remains a good
> > rule-of-thumb.
> 
> ---
>     Ug.  I like to view swap as "low grade memory" -- i.e. I really
> should spend 99.9% of my time in RAM -- if I spill, then it means
> I'm running too much/too big for my computer and should get more RAM --
> meanwhile, I suffer with performance degradation to remind me I'm really
> exceeding my machine's physical memory capacity.

Agreed. However, with current growing memory sizes, people are
suggesting: "I ran with 32Mb RAM and 64Mb swap until a year ago, so
128Mb ram should allow me to run swapless". I disagree.

The price-difference between RAM and disk is such (*) that if you
follow the guideline of swap=2xRAM, you're still spending 20 to 50
times as much on the RAM as you are on the disk space for swap.

Even if the swap is going to be idle 99.9% of the time, the investment
allows you to say "gosh what is the machien slow today. It might be
swapping" instead of "Why the heck has the machine crashed (#) all of
a sudden."

			Rogier. 

(*) And remains like that!

(#) Even if we have a good OOM killer, you might find the machine in a
non-workable state.

-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots. 
* There are also old, bald pilots. 

  parent reply	other threads:[~2001-04-28  7:47 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-02 21:23 2.4 and 2GB swap partition limit Matt_Domsch
2001-03-02 23:52 ` Kenneth Johansson
2001-03-03  6:14 ` William T Wilson
2001-03-03 11:14   ` Rogier Wolff
2001-03-08 13:05     ` Goswin Brederlow
2001-04-27 10:51       ` Xavier Bestel
2001-04-27 11:13         ` Rogier Wolff
2001-04-27 20:52           ` LA Walsh
2001-04-27 21:44             ` Rik van Riel
2001-04-27 22:06               ` Thomas Dodd
2001-04-27 22:40               ` Hugh Dickins
2001-04-27 22:40                 ` Rik van Riel
2001-04-29 15:12                 ` Ingo Oeser
2001-04-27 22:44               ` LA Walsh
2001-04-28  7:47             ` Rogier Wolff [this message]
2001-04-27 22:22           ` Wakko Warner
2001-04-28 13:17             ` Rogier Wolff
2001-04-28 13:37               ` Wakko Warner
2001-04-28 14:11                 ` Rogier Wolff
2001-04-28 14:28                   ` J . A . Magallon
2001-04-30 18:12                     ` Alan Cox
2001-05-01 13:00                       ` Stephen C. Tweedie
2001-05-01 16:14                         ` Rogier Wolff
2001-05-01 16:35                           ` Stephen C. Tweedie
2001-05-02 10:54                             ` Rogier Wolff
2001-05-02 11:04                               ` Stephen C. Tweedie
2001-05-02 12:49                                 ` Hugh Dickins
2001-05-02 13:43                                   ` Stephen C. Tweedie
2001-05-02  0:28                         ` Rik van Riel
2001-05-02  0:34                           ` David S. Miller
2001-05-02  0:43                             ` Rik van Riel
2001-05-02  1:14                               ` Roger Larsson
2001-05-02  1:30                                 ` Rik van Riel
2001-05-01 13:39                       ` Christoph Rohland
2001-05-01 23:25                         ` Rik van Riel
2001-04-28 18:04                   ` Albert D. Cahalan
2001-04-28 21:23                     ` Rogier Wolff
2001-04-29  1:43                     ` Jonathan Lundell
2001-04-29  9:17                       ` Kenneth Johansson
2001-04-28 18:21                   ` David Lang
2001-04-28 21:25                     ` Rogier Wolff
2001-04-30 18:14               ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2001-03-04 22:04 Matt_Domsch
2001-03-05  8:58 ` Christoph Rohland
2001-03-05 14:30   ` Rik van Riel
2001-03-05 14:36   ` Rik van Riel
2001-03-05 14:52   ` Matti Aarnio
2001-03-05 13:30 ` Christoph Hellwig
2001-03-05 16:53 Andries.Brouwer
2001-04-30 18:45 Torrey Hoffman
2001-04-30 19:04 ` Richard B. Johnson
2001-04-30 19:07   ` David S. Miller
2001-04-30 19:14     ` Richard B. Johnson
2001-04-30 21:04       ` Andreas Ferber
2001-05-02 14:31     ` Andi Kleen
2001-05-02 22:17       ` Andreas Dilger
2001-05-04  8:16         ` Andi Kleen
2001-05-03 14:04 Ishikawa

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=200104280747.JAA03559@cave.bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=Matt_Domsch@Dell.com \
    --cc=fluffy@snurgle.org \
    --cc=goswin.brederlow@student.uni-tuebingen.de \
    --cc=law@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xavier.bestel@free.fr \
    /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