From: Hans Reiser <reiser@namesys.com>
To: Russell Coker <russell@coker.com.au>
Cc: linux-ide-arrays@lists.math.uh.edu,
ReiserFS <reiserfs-list@namesys.com>,
mikej@umem.com, Edward Shishkin <edward@namesys.com>
Subject: Re: non volatile ram devices
Date: Thu, 05 Dec 2002 01:05:58 +0300 [thread overview]
Message-ID: <3DEE7C46.9080203@namesys.com> (raw)
In-Reply-To: <200212042059.35300.russell@coker.com.au>
Russell Coker wrote:
>I have some servers that are giving inadequate disk performance for Maildir
>mail spools. They are running kernel 2.4.19 (2.4.20 upgrade is planned) and
>using ReiserFS for everything that's important.
>
>At this stage it is impossible for me to replace disks, RAID controllers, or
>anything else really significant.
>
>What I am thinking of doing is using a kernel that supports data journalling
>which should increase performance, but still probably won't give me enough.
>So I am thinking of using an "external journal" (or using software RAID to
>put the part of the partition containing the journal on a different device).
>
>The device containing the journal would be something much faster than physical
>media. I have been doing some research on non-volatile memory devices. I
>only found one company producing disks that are RAM based with battery
>backup, and they seem to start at $10K (too expensive - probably because they
>are much larger than I need, I need 128M at most, they provide 2G). I found
>many companies selling flash memory, but that only takes a million writes
>(that'll last about an hour for the use I plan). I found one company selling
>PC-Card devices that have two batterys for backup, but that requires getting
>a PCI controller for PC-Card's (something I haven't tried before).
>
>Does anyone know of an affordable ($1000 or less) device that can survive
>unexpected power outages of at least 24 hours duration, can commit a write in
>less than 1ms, supports unlimited writes, and connects to a IDE or SCSI bus
>(or PCI if there's a suitable Linux driver).
>
>
>
The umem.com folks sell a device that we have tested and benchmarked
reiserfs on. If I could get Edward to format benchmarks in a way that
conveys that information that is relevant to persons reading them, I
would post them on our mailing list....
Hans
next prev parent reply other threads:[~2002-12-04 22:05 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
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 [this message]
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=3DEE7C46.9080203@namesys.com \
--to=reiser@namesys.com \
--cc=edward@namesys.com \
--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.