From: "Ragnar Kjørstad" <reiserfs@ragnark.vestdata.no>
To: Russell Coker <russell@coker.com.au>
Cc: linux-ide-arrays@lists.math.uh.edu,
ReiserFS <reiserfs-list@namesys.com>, Mike Jadon <mikej@umem.com>
Subject: Re: non volatile ram devices
Date: Thu, 5 Dec 2002 11:38:26 +0100 [thread overview]
Message-ID: <20021205113826.B25528@vestdata.no> (raw)
In-Reply-To: <200212051000.32340.russell@coker.com.au>; from russell@coker.com.au on Thu, Dec 05, 2002 at 10:00:32AM +0100
On Thu, Dec 05, 2002 at 10:00:32AM +0100, Russell Coker wrote:
> > Even if the device is just a regular disk it should give you a real
> > performance boost. Depending on your RAID-setup, it may not be the
> > throughput, but the seeking back and forth between the journal and the
> > rest of the disk that kills performance. Having the journal on a
> > seperate disk solves that problem.
>
> True. However I could only put in a single extra disk, and I don't want to
> use non-RAID...
Unless you use two ramdisks you still have a single point of failure.
Not sure exactly how the reability of the ramdrive is compared to a
disk?
--
Ragnar Kjørstad
next prev parent reply other threads:[~2002-12-05 10:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 19:59 non volatile ram devices Russell Coker
2002-12-04 20:24 ` Ragnar Kjørstad
2002-12-05 9:00 ` Russell Coker
2002-12-05 10:38 ` Ragnar Kjørstad [this message]
2002-12-05 10:45 ` Russell Coker
2002-12-05 13:23 ` Chris Mason
2002-12-06 9:52 ` Russell Coker
2002-12-06 13:03 ` Chris Mason
2002-12-06 23:53 ` Matthias Andree
2002-12-06 23:50 ` Matthias Andree
2002-12-07 4:09 ` Todd Lyons
2002-12-07 17:13 ` Matthias Andree
2002-12-07 10:03 ` Russell Coker
2002-12-07 10:44 ` Valdis.Kletnieks
2002-12-04 22:05 ` Hans Reiser
2002-12-04 21:17 ` Mike Jadon
2002-12-05 6:32 ` Oleg Drokin
2002-12-05 8:36 ` Russell Coker
2002-12-05 16:21 ` Todd Lyons
2002-12-05 22:51 ` Russell Coker
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=20021205113826.B25528@vestdata.no \
--to=reiserfs@ragnark.vestdata.no \
--cc=linux-ide-arrays@lists.math.uh.edu \
--cc=mikej@umem.com \
--cc=reiserfs-list@namesys.com \
--cc=russell@coker.com.au \
/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.