From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Ignacio Vazquez-Abrams <ignacio@openservices.net>
Cc: "Eric S. Raymond" <esr@thyrsus.com>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
gars@lanm-pc.com
Subject: Re: Swap size for a machine with 2GB of memory
Date: Sun, 19 Aug 2001 18:15:41 +0200 [thread overview]
Message-ID: <20010819181541.L9870@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <20010819024233.A26916@thyrsus.com> <Pine.LNX.4.33.0108190526090.4118-100000@terbidium.openservices.net>
In-Reply-To: <Pine.LNX.4.33.0108190526090.4118-100000@terbidium.openservices.net>; from ignacio@openservices.net on Sun, Aug 19, 2001 at 05:46:32AM -0400
On Sun, Aug 19, 2001 at 05:46:32AM -0400, Ignacio Vazquez-Abrams wrote:
> At the other extreme, I've heard of machines that are running heavy scientific
> applications. They have 4 GB of RAM and run with 10+ GB of swap.
>
> A machine with 2 GB of RAM can easily live with no swap, unless you want to
> run web, proxy, or database servers in very large configurations, or if you
> compile software several times the size of XFree86 with any regularity. By
> "very large configurations" I mean something you would have to deliberately
> set, probably requiring a change to defined constants in the software.
One word here: tmpfs.
I use several amounts of RAM as tmpfs. And with that you can
certainly reach the point of swapping sth. out.
But my machine has only 1GB of RAM and I set up only 2GB of swap.
I compile and test many things there directly from the CVS, run
things like the fcgp to produce nearly a GB of PostScript files
and many more fun things.
So if you plan to use tmpfs, better have enough swap available.
Files in tmpfs can also not be removed by the OOM killer. So you
should define your tmpfs limits properly.
Regards
Ingo Oeser
--
Isn't vi that text editor with two modes... one that beeps and one
that corrupts your file? --- Dan Jacobson in comp.os.linux.advocacy
next prev parent reply other threads:[~2001-08-19 16:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-19 6:42 Swap size for a machine with 2GB of memory Eric S. Raymond
2001-08-19 8:25 ` Andrzej Krzysztofowicz
2001-08-19 9:46 ` Ignacio Vazquez-Abrams
2001-08-19 16:15 ` Ingo Oeser [this message]
2001-08-19 14:08 ` Alan Cox
2001-08-19 16:48 ` Eric S. Raymond
2001-08-19 14:39 ` Steven Cole
2001-08-19 17:29 ` Luigi Genoni
2001-08-19 15:52 ` Steven Cole
2001-08-19 22:16 ` Luigi Genoni
2001-08-19 20:49 ` Eric W. Biederman
2001-08-19 21:15 ` Eric S. Raymond
2001-08-20 0:05 ` Kevin Krieser
2001-08-20 17:42 ` Eric W. Biederman
2001-08-20 23:09 ` Kevin Krieser
-- strict thread matches above, loose matches on Subject: below --
2001-08-20 0:08 Andries.Brouwer
2001-08-21 23:14 ` Kurt Garloff
2001-08-24 12:45 ` Rogier Wolff
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=20010819181541.L9870@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=esr@thyrsus.com \
--cc=gars@lanm-pc.com \
--cc=ignacio@openservices.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.