public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Blueman <daniel.blueman@gmail.com>
To: Tobias Oetiker <tobi@oetiker.ch>
Cc: Florian Weimer <fweimer@bfk.de>, linux-btrfs@vger.kernel.org
Subject: Re: Benchmarking btrfs on HW Raid ... BAD
Date: Mon, 28 Sep 2009 10:19:37 +0100	[thread overview]
Message-ID: <6278d2220909280219h5b38577eqc1bee1a26cbc93e1@mail.gmail.com> (raw)
In-Reply-To: <82tyynxz2g.fsf@mid.bfk.de>

On Mon, Sep 28, 2009 at 9:17 AM, Florian Weimer <fweimer@bfk.de> wrote:
> * Tobias Oetiker:
>
>> Running this on a single disk, I get the quite acceptable results.
>> When running on-top of a Areca HW Raid6 (lvm partitioned)
>> then both read and write performance go down by at least 2
>> magnitudes.
>
> Does the HW RAID use write caching (preferably battery-backed)?

I believe Areca controllers have an option for writeback or
writethrough caching, so it's worth checking this and that you're
running the current firmware, in case of errata. Ironically, disabling
writeback will give the OS tighter control of request latency, but
throughput may drop a lot. I still can't help thinking that this is
down to the behaviour of the controller, due to the 1-disk case
working well.

One way would be to configure the array as 6 or 7 devices, and allow
BTRFS/DM to mange the array, then see if performance under write load
is better, and with or without writeback caching...

Daniel
-- 
Daniel J Blueman

  parent reply	other threads:[~2009-09-28  9:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-28  8:06 Benchmarking btrfs on HW Raid ... BAD Tobias Oetiker
2009-09-28  8:17 ` Florian Weimer
2009-09-28  9:19   ` Tobias Oetiker
2009-09-28  9:19   ` Daniel J Blueman [this message]
2009-09-28  9:39     ` Tobias Oetiker
2009-09-30 14:35       ` Ric Wheeler
2009-09-30 18:44         ` Tobias Oetiker

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=6278d2220909280219h5b38577eqc1bee1a26cbc93e1@mail.gmail.com \
    --to=daniel.blueman@gmail.com \
    --cc=fweimer@bfk.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=tobi@oetiker.ch \
    /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