From: John Robinson <john.robinson@anonymous.org.uk>
To: thomas@fjellstrom.ca
Cc: stan@hardwarefreak.com, Tommy Apel Hansen <tommyapeldk@gmail.com>,
Chris Murphy <lists@colorremedies.com>,
linux-raid Raid <linux-raid@vger.kernel.org>
Subject: Re: recommended way to add ssd cache to mdraid array
Date: Wed, 16 Jan 2013 08:59:07 +0000 [thread overview]
Message-ID: <50F66BDB.3000203@anonymous.org.uk> (raw)
In-Reply-To: <201301152231.43704.thomas@fjellstrom.ca>
On 16/01/2013 05:31, Thomas Fjellstrom wrote:
> On Tue Jan 15, 2013, Stan Hoeppner wrote:
>> On 1/14/2013 9:52 PM, Thomas Fjellstrom wrote:
>> ...
>>> It is working. And I can live with it as is, but it does seem like
>>> something isn't right. If thats just me jumping to conclusions, well
>>> thats fine then. But 600MB/s+ reads vs 200MB/s writes seems a tad off.
>>
>> It's not off. As myself and others stated previously, this low write
>> performance is typical of RAID6, particularly for unaligned or partial
>> stripe writes--anything that triggers a RMW cycle.
>
> That gets me thinking. Maybe try a test with the record test size set to the
> stripe width, that would hopefully show some more accurate numbers.
Your 7-drive RAID-6 with 512K chunk will have a 2.5MB stripe width, or
stride, whichever is the correct term, on the basis of 5 data chunks.
Even still, a filesystem-level test cannot guarantee to be writing
records aligned to the array's data stripes.
If you do another benchmark, try running iostat concurrently, to see how
many reads are happening during the write tests.
At the same time, if in the real world you're doing streaming writes of
dozens of MB/s, I would expect that write caching would turn a good
proportion of the writes into full-stripe writes.
Cheers,
John.
next prev parent reply other threads:[~2013-01-16 8:59 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-22 6:57 recommended way to add ssd cache to mdraid array Thomas Fjellstrom
2012-12-23 3:44 ` Thomas Fjellstrom
2013-01-09 18:41 ` Thomas Fjellstrom
2013-01-10 6:25 ` Chris Murphy
2013-01-10 10:49 ` Thomas Fjellstrom
2013-01-10 21:36 ` Chris Murphy
2013-01-11 0:18 ` Stan Hoeppner
2013-01-11 12:35 ` Thomas Fjellstrom
2013-01-11 12:48 ` Thomas Fjellstrom
2013-01-14 0:05 ` Tommy Apel Hansen
2013-01-14 8:58 ` Thomas Fjellstrom
2013-01-14 18:22 ` Thomas Fjellstrom
2013-01-14 19:45 ` Stan Hoeppner
2013-01-14 21:53 ` Thomas Fjellstrom
2013-01-14 22:51 ` Chris Murphy
2013-01-15 3:25 ` Thomas Fjellstrom
2013-01-15 1:50 ` Stan Hoeppner
2013-01-15 3:52 ` Thomas Fjellstrom
2013-01-15 8:38 ` Stan Hoeppner
2013-01-15 9:02 ` Tommy Apel
2013-01-15 11:19 ` Stan Hoeppner
2013-01-15 10:47 ` Tommy Apel
2013-01-16 5:31 ` Thomas Fjellstrom
2013-01-16 8:59 ` John Robinson [this message]
2013-01-16 21:29 ` Stan Hoeppner
2013-02-10 6:59 ` Thomas Fjellstrom
2013-01-16 22:06 ` Stan Hoeppner
2013-01-14 21:38 ` Tommy Apel Hansen
2013-01-14 21:47 ` Tommy Apel Hansen
2013-01-11 12:20 ` Thomas Fjellstrom
2013-01-11 17:39 ` Chris Murphy
2013-01-11 17:46 ` Chris Murphy
2013-01-11 18:52 ` Thomas Fjellstrom
2013-01-12 0:47 ` Phil Turmel
2013-01-12 3:56 ` Chris Murphy
2013-01-13 22:13 ` Phil Turmel
2013-01-13 23:20 ` Chris Murphy
2013-01-14 0:23 ` Phil Turmel
2013-01-14 3:58 ` Chris Murphy
2013-01-14 22:00 ` Thomas Fjellstrom
2013-01-11 18:51 ` Thomas Fjellstrom
2013-01-11 22:17 ` Stan Hoeppner
2013-01-12 2:44 ` Thomas Fjellstrom
2013-01-12 8:33 ` Stan Hoeppner
2013-01-12 14:44 ` Thomas Fjellstrom
2013-01-13 19:18 ` Chris Murphy
2013-01-14 9:06 ` Thomas Fjellstrom
2013-01-11 18:50 ` Stan Hoeppner
2013-01-12 2:45 ` Thomas Fjellstrom
2013-01-12 12:06 ` Roy Sigurd Karlsbakk
2013-01-12 14:14 ` Stan Hoeppner
2013-01-12 16:37 ` Roy Sigurd Karlsbakk
2013-01-10 13:13 ` Brad Campbell
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=50F66BDB.3000203@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=stan@hardwarefreak.com \
--cc=thomas@fjellstrom.ca \
--cc=tommyapeldk@gmail.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).