From: "Jakob Østergaard" <jakob@unthought.net>
To: "G. Hugh Song" <ghsong@kjist.ac.kr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Plain 2.4.5 VM...
Date: Tue, 29 May 2001 06:57:37 +0200 [thread overview]
Message-ID: <20010529065737.E29962@unthought.net> (raw)
In-Reply-To: <200105290232.f4T2W9m00876@bellini.kjist.ac.kr> <20010529061039.D29962@unthought.net> <3B1329A4.E72D9D62@kjist.ac.kr>
In-Reply-To: <3B1329A4.E72D9D62@kjist.ac.kr>; from ghsong@kjist.ac.kr on Tue, May 29, 2001 at 01:46:28PM +0900
On Tue, May 29, 2001 at 01:46:28PM +0900, G. Hugh Song wrote:
> Jakob,
>
> My Alpha has 2GB of physical memory. In this case how much swap space
> should
> I assign in these days of kernel 2.4.*? I had had trouble with 1GB of
> swap space
> before switching back to 2.2.20pre2aa1.
If you run a single mingetty and bash session, you need no swap.
If you run four 1GB processes concurrently, I would use ~5-6G of swap to be on
the safe side.
Swap is very cheap, even if measured in gigabytes. Go with the sum of the
largest process foot-prints you can imagine running on your system, and then
add some. Be generous. It's not like unused swap space is going to slow the
system down - it's a nice extra little safety to have. It's beyond me why
anyone would run a system with marginal swap.
On a compile box here with 392 MB physical, I have 900 MB swap. This
accomodates multiple concurrent 100-300 MB compile jobs. Never had a problem.
Oh, and I didn't have to change my swap setup between 2.2 and 2.4.
--
................................................................
: jakob@unthought.net : And I see the elder races, :
:.........................: putrid forms of man :
: Jakob Østergaard : See him rise and claim the earth, :
: OZ9ABN : his downfall is at hand. :
:.........................:............{Konkhra}...............:
next prev parent reply other threads:[~2001-05-29 4:58 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 2:32 Plain 2.4.5 VM G. Hugh Song
2001-05-29 4:10 ` Jakob Østergaard
2001-05-29 4:26 ` safemode
2001-05-29 4:38 ` Jeff Garzik
2001-05-29 6:04 ` Mike Galbraith
2001-05-29 14:06 ` Gerhard Mack
2001-05-29 4:46 ` G. Hugh Song
2001-05-29 4:57 ` Jakob Østergaard [this message]
2001-05-29 7:13 ` Marcelo Tosatti
2001-05-29 9:10 ` Alan Cox
2001-05-29 15:37 ` elko
2001-05-29 20:09 ` Plain 2.4.5 VM... (and 2.4.5-ac3) Vincent Stemen
2001-05-29 20:16 ` Alan Cox
2001-05-29 21:36 ` Vincent Stemen
2001-05-30 6:02 ` Mike Galbraith
2001-05-30 19:58 ` Vincent Stemen
2001-05-30 20:11 ` Alan Cox
2001-05-30 20:17 ` Mike Galbraith
2001-05-31 3:47 ` Vincent Stemen
2001-05-31 6:18 ` Mike Galbraith
2001-05-30 20:30 ` Rik van Riel
2001-05-31 3:11 ` Vincent Stemen
[not found] ` <991254700.786.0.camel@tux.bitfreak.net>
2001-05-30 21:59 ` Vincent Stemen
2001-05-30 20:16 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2001-05-30 4:24 Plain 2.4.5 VM Craig Kulesa
2001-05-30 6:50 ` Mike Galbraith
2001-05-30 13:27 ` Jonathan Morton
2001-05-30 12:20 ` Marcelo Tosatti
2001-05-30 15:27 ` Mike Galbraith
2001-05-30 18:39 ` Rik van Riel
2001-05-30 17:19 ` Marcelo Tosatti
2001-05-30 20:33 ` Mike Galbraith
2001-05-30 19:25 ` Marcelo Tosatti
2001-05-31 5:20 ` Mike Galbraith
2001-05-30 15:18 ` Mike Galbraith
2001-05-30 19:16 ` Rik van Riel
[not found] <mailman.991098720.29883.linux-kernel2news@redhat.com>
2001-05-29 2:55 ` Pete Zaitcev
2001-05-29 0:32 Jeff Garzik
2001-05-29 1:13 ` Mohammad A. Haque
2001-05-29 1:14 ` Mohammad A. Haque
2001-05-29 8:51 ` Alan Cox
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=20010529065737.E29962@unthought.net \
--to=jakob@unthought.net \
--cc=ghsong@kjist.ac.kr \
--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