All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ragnar Kjørstad" <linux-ide-arrays@ragnark.vestdata.no>
To: Russell Coker <russell@coker.com.au>
Cc: linux-ide-arrays@lists.math.uh.edu, ReiserFS <reiserfs-list@namesys.com>
Subject: Re: non volatile ram devices
Date: Wed, 4 Dec 2002 21:24:47 +0100	[thread overview]
Message-ID: <20021204212447.C20004@vestdata.no> (raw)
In-Reply-To: <200212042059.35300.russell@coker.com.au>; from russell@coker.com.au on Wed, Dec 04, 2002 at 08:59:35PM +0100

On Wed, Dec 04, 2002 at 08:59:35PM +0100, 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.

One thing you might considder is replacing the reiserfs hash with a
maildir-specific hash. In my rather limited testing I found that it was
significantly faster; I think some tests gave 200-300% speed
improvement.

But, as I said, there was only limited testing. Don't go this route
unless you have the time to test it properly both for stability and
performance.


> 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.

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.


> 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).

Did you check out Micro Memory Inc? (http://www.umem.com/) 
I think they have some PCI-cards (with linux-drivers) which may be
suitable for this. 

However, the main strength of flash/RAM devices is that you can do
random writes very fast. For a journal deice all access will be
sequential, so there may not be much advantage compared to using a
seperate disk for the journal? I've never tried, so I'm not sure exactly
how well it would work.

Is your server read- or write- bound? I've found that some mailservers
are IO-bound because of reads (I guess pop- and imap-servers that are
polling), and then the external journal is not likely to help.



-- 
Ragnar Kjørstad

  reply	other threads:[~2002-12-04 20:24 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 [this message]
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
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=20021204212447.C20004@vestdata.no \
    --to=linux-ide-arrays@ragnark.vestdata.no \
    --cc=linux-ide-arrays@lists.math.uh.edu \
    --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.