Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Tommy Apel <tommyapeldk@gmail.com>
Cc: Andrei Banu <andrei.banu@redhost.ro>,
	linux-raid Raid <linux-raid@vger.kernel.org>
Subject: Re: Incredibly poor performance of mdraid-1 with 2 SSD Samsung 840 PRO
Date: Sun, 21 Apr 2013 19:47:51 -0500	[thread overview]
Message-ID: <517488B7.9030505@hardwarefreak.com> (raw)
In-Reply-To: <CAGA4a+Fsrum9vrtWbeKP4jWfT3JAAMK4Ci1HU6A2cMez1mwttw@mail.gmail.com>

On 4/21/2013 2:56 PM, Tommy Apel wrote:
> Calm the f. down, I was just handing over some information, sorry your
> day was ruined mr. high and mighty, use the info for whatever you want
> to but flaming me is't going to help anyone.

Your tantrum aside, the Intel 330, as well as all current Intel SSDs,
uses the SandForce 2281 controller.  The SF2xxx series' write
performance is limited by the compressibility of the data.  What you're
doing below is simply showcasing the write bandwidth limitation of the
SF2xxx controllers with incompressible data.

This is not relevant to md.  And it's not relevant to Andrei.  It turns
out that the Samsung 840 SSDs have consistent throughput because they
don't rely on compression.

-- 
Stan


> 2013/4/21 Stan Hoeppner <stan@hardwarefreak.com>:
>> On 4/21/2013 7:23 AM, Tommy Apel wrote:
>>> Hello, FYI I'm getting ~68MB/s on two intel330 in RAID1 aswell on
>>> vanilla 3.8.8 and 3.9.0-rc3 when writing random data and ~236MB/s
>>> writing from /dev/zero
>>>
>>> mdadm -C /dev/md0 -l 1 -n 2 --assume-clean --force --run /dev/sdb /dev/sdc
>>
>>
>>> openssl enc -aes-128-ctr -pass pass:"$(dd if=/dev/urandom bs=128
>>> count=1 2>/dev/null | base64)" -nosalt < /dev/zero | pv -pterb >
>>> /run/fill ~1.06GB/s
>>
>> What's the purpose of all of this?  Surely not simply to create random
>> data, which is accomplished much more easily.  Are you sand bagging us
>> here with a known bug, or simply trying to show off your mad skillz?
>> Either way this is entirely unnecessary for troubleshooting an IO
>> performance issue.  dd doesn't (shouldn't) care if the bits are random
>> or not, though the Intel SSD controller might, as well as other layers
>> you may have in your IO stack.  Keep it simple so we can isolate one
>> layer at a time.
>>
>>> dd if=/run/fill of=/dev/null bs=1M count=1024 iflag=fullblock ~5.7GB/s
>>> dd if=/run/fill of=/dev/md0 bs=1M count=1024 oflag=direct ~68MB/s
>>> dd if=/dev/zero of=/dev/md0 bs=1M count=1024 oflag=direct ~236MB/s
>>
>> Noting the above, it's interesting that you omitted this test
>>
>>   dd if=/run/fill of=/dev/sdb bs=1M count=1024 oflag=direct
>>
>> preventing an apples to apples comparison between raw SSD device and
>> md/RAID1 performance with your uber random file as input.
>>
>> --
>> Stan
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


  reply	other threads:[~2013-04-22  0:47 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19 22:58 Incredibly poor performance of mdraid-1 with 2 SSD Samsung 840 PRO Andrei Banu
     [not found] ` <CAH3kUhEaZGON=fAyVMZOz5fH_DcfKv=hCa96UCeK4pN7k81c_Q@mail.gmail.com>
2013-04-20 23:26   ` Andrei Banu
     [not found]   ` <51725458.7020109@redhost.ro>
     [not found]     ` <CAH3kUhHxBiqugFQm=PPJNNe9jOdKy0etUjQNsoDz_LJNUCLCCQ@mail.gmail.com>
2013-04-20 23:25       ` Andrei Banu
2013-04-20 23:26       ` Andrei Banu
2013-04-21  2:48         ` Stan Hoeppner
2013-04-21 12:23           ` Tommy Apel
2013-04-21 16:48             ` Tommy Apel
2013-04-21 19:33             ` Stan Hoeppner
2013-04-21 19:56               ` Tommy Apel
2013-04-22  0:47                 ` Stan Hoeppner [this message]
2013-04-22  7:51                   ` Tommy Apel
2013-04-22  8:29                     ` Tommy Apel
2013-04-22 10:26                     ` Andrei Banu
2013-04-22 12:02                       ` Tommy Apel
2013-04-23  2:59                         ` Stan Hoeppner
2013-04-22 23:21                     ` Stan Hoeppner
2013-04-25 11:38         ` Thomas Jarosch
2013-04-21  0:10 ` Stan Hoeppner
     [not found] ` <51732E2B.6090607@hardwarefreak.com>
2013-04-21 20:46   ` Andrei Banu
2013-04-21 23:17     ` Stan Hoeppner
2013-04-22 10:19       ` Andrei Banu
2013-04-23  2:51         ` Stan Hoeppner
2013-04-23 10:17           ` Andrei Banu
2013-04-24  3:24             ` Stan Hoeppner
2013-04-24  8:26               ` Andrei Banu
2013-04-24  9:12                 ` Adam Goryachev
2013-04-24 10:24                   ` Tommy Apel
2013-04-24 21:42                     ` Andrei Banu
2013-04-24 21:40                   ` Andrei Banu
2013-04-24 16:37                 ` Stan Hoeppner
2013-04-24 21:46                   ` Andrei Banu
     [not found]                     ` <CAH3kUhHnF0imY=CAHfzaQy4XJuOMgOtbHNp17EYzeSJR2en7Fg@mail.gmail.com>
2013-04-25 10:11                       ` Andrei Banu
2013-04-25 10:56                     ` Stan Hoeppner
2013-04-22 23:11       ` Andrei Banu
2013-04-23  4:39         ` Stan Hoeppner
2013-04-22 23:25       ` Stan Hoeppner
2013-04-23  4:49         ` Mikael Abrahamsson
2013-04-23  6:01 ` Stan Hoeppner

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=517488B7.9030505@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=andrei.banu@redhost.ro \
    --cc=linux-raid@vger.kernel.org \
    --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