From: Andreas Dilger <adilger@turbolabs.com>
To: Michael Peddemors <michael@wizard.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Current Max Swap size? Performance issues
Date: Fri, 16 Nov 2001 16:33:46 -0700 [thread overview]
Message-ID: <20011116163346.L1308@lynx.no> (raw)
In-Reply-To: <1005948151.10803.18.camel@mistress>
In-Reply-To: <1005948151.10803.18.camel@mistress>; from michael@wizard.ca on Fri, Nov 16, 2001 at 02:02:31PM -0800
On Nov 16, 2001 14:02 -0800, Michael Peddemors wrote:
> With all of the latest VM, again the question is asked... Best way to
> set up swap now..
>
> For 2 GIG memory...
> Channel 0 is RAID 1 SCSI
> Channel 2 is RAID 1+0 SCSI
> Hardware Raid
>
> Shoudl it be?
>
> 2 GIG swap partition (Is this still the limit?)
Yes, still the limit. It turns out that this is not an on-disk format
limit, but rather an in-memory structure limit, in case you cared. For
non-x86 platforms, there is a different limit.
> Dual 2 GIG swaps on seperate channels?
> Dual 2 GIG swap files on same channel?
> (Assuming that the channel is different than the channel using the bulk
> of I/O)
Well, if you have the hardware for it, obviously separate channels will
be better, as long as you don't get a lot of I/O contention. If you
put them on the same channel, but different disks, you still will get
some speedup if the swaps are equal priority. If they are sharing the
same disk, make sure you have different priorities for the swaps, so
that one gets filled before the other, or you will get a LOT of seeking
going on.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2001-11-16 23:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 22:02 Current Max Swap size? Performance issues Michael Peddemors
2001-11-16 23:33 ` Andreas Dilger [this message]
2001-11-18 6:28 ` Eric W. Biederman
2001-11-19 9:48 ` Andreas Dilger
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=20011116163346.L1308@lynx.no \
--to=adilger@turbolabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@wizard.ca \
/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