From: "Barry K. Nathan" <barryn@pobox.com>
To: Chase Venters <chase.venters@clientec.com>
Cc: Michael Loftis <mloftis@wgops.com>, Al Boldi <a1426z@gawab.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] VM: I have a dream...
Date: Mon, 23 Jan 2006 00:20:16 -0800 [thread overview]
Message-ID: <986ed62e0601230020g19dfe825r1b81a2bed411c1fc@mail.gmail.com> (raw)
In-Reply-To: <200601222346.24781.chase.venters@clientec.com>
On 1/22/06, Chase Venters <chase.venters@clientec.com> wrote:
> Just as a curiosity... does anyone have any guesses as to the runtime
> performance cost of hosting one or more swap files (which thanks to on demand
> creation and growth are presumably built of blocks scattered around the disk)
> versus having one or more simple contiguous swap partitions?
>
> I think it's probably a given that swap partitions are better; I'm just
> curious how much better they might actually be.
If you google "mac os x swap partition", you'll find benchmarks from
several years ago. (Although, those benchmarks are with a partition
dedicated to the dynamically created swap files. It does more or less
ensure that the files are contiguous though.) Mac OS X was *much* more
of a dog back then, in terms of performance, so I don't know how
relevant those benchmarks are nowadays, but it might be a starting
point for answering your question.
--
-Barry K. Nathan <barryn@pobox.com>
next prev parent reply other threads:[~2006-01-23 8:20 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-21 18:08 [RFC] VM: I have a dream Al Boldi
2006-01-21 18:42 ` Jamie Lokier
2006-01-21 18:46 ` Avi Kivity
2006-01-23 19:52 ` Bryan Henderson
2006-01-25 22:04 ` Al Boldi
2006-01-26 19:18 ` Bryan Henderson
2006-01-27 16:12 ` Al Boldi
2006-01-27 19:17 ` Bryan Henderson
2006-01-30 13:21 ` Al Boldi
2006-01-30 13:35 ` Kyle Moffett
2006-01-31 15:56 ` Al Boldi
2006-01-31 16:34 ` Kyle Moffett
2006-01-31 23:14 ` Bryan Henderson
2006-01-31 16:34 ` Lennart Sorensen
2006-01-31 19:23 ` Jamie Lokier
2006-02-01 4:06 ` Barry K. Nathan
2006-02-02 15:11 ` Alan Cox
2006-02-02 18:59 ` Al Boldi
2006-02-02 22:33 ` Bryan Henderson
2006-02-03 14:46 ` Alan Cox
2006-01-30 16:49 ` Bryan Henderson
2006-01-26 0:03 ` Jon Smirl
2006-01-26 19:48 ` Bryan Henderson
2006-01-22 8:16 ` Pavel Machek
2006-01-22 12:33 ` Robin Holt
2006-01-23 18:03 ` Al Boldi
2006-01-23 18:40 ` Valdis.Kletnieks
2006-01-23 19:26 ` Benjamin LaHaise
2006-01-23 19:40 ` Valdis.Kletnieks
2006-01-23 22:26 ` Pavel Machek
2006-01-22 19:55 ` Barry K. Nathan
2006-01-23 5:23 ` Michael Loftis
2006-01-23 5:46 ` Chase Venters
2006-01-23 8:20 ` Barry K. Nathan [this message]
2006-01-23 13:17 ` Jamie Lokier
2006-01-23 20:21 ` Peter Chubb
2006-01-23 15:05 ` Ram Gupta
2006-01-23 15:26 ` Diego Calleja
2006-01-23 16:11 ` linux-os (Dick Johnson)
2006-01-23 16:50 ` Jamie Lokier
2006-01-24 2:08 ` Horst von Brand
2006-01-25 6:13 ` Jamie Lokier
2006-01-25 9:23 ` Bernd Petrovitsch
2006-01-25 9:42 ` Lee Revell
2006-01-25 15:02 ` Jamie Lokier
2006-01-25 23:24 ` Lee Revell
2006-01-25 15:05 ` Jamie Lokier
2006-01-25 15:47 ` Bernd Petrovitsch
2006-01-25 16:09 ` Diego Calleja
2006-01-25 17:26 ` Jamie Lokier
2006-01-26 19:13 ` Bryan Henderson
2006-01-25 23:28 ` Lee Revell
2006-01-26 1:29 ` Diego Calleja
2006-01-26 5:01 ` Jamie Lokier
2006-01-26 5:11 ` Lee Revell
2006-01-26 14:46 ` Dave Kleikamp
2006-01-24 2:10 ` Horst von Brand
2006-01-25 22:27 ` Nix
2006-01-26 15:13 ` Denis Vlasenko
2006-01-26 16:23 ` Nix
2006-01-23 20:43 ` Michael Loftis
2006-01-23 22:42 ` Nikita Danilov
2006-01-24 14:36 ` Ram Gupta
2006-01-24 15:04 ` Diego Calleja
2006-01-24 20:59 ` Bryan Henderson
2006-01-24 15:11 ` Nikita Danilov
2006-01-23 22:57 ` Ram Gupta
-- strict thread matches above, loose matches on Subject: below --
2006-02-01 13:58 Al Boldi
2006-02-01 14:38 ` Jamie Lokier
2006-02-02 12:26 ` Al Boldi
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=986ed62e0601230020g19dfe825r1b81a2bed411c1fc@mail.gmail.com \
--to=barryn@pobox.com \
--cc=a1426z@gawab.com \
--cc=chase.venters@clientec.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mloftis@wgops.com \
/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;
as well as URLs for NNTP newsgroup(s).