All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: Iustin Pop <iusty@k1024.org>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: standard performance (write speed 20Mb/s)
Date: Sun, 17 Jul 2011 13:51:11 +0100	[thread overview]
Message-ID: <4E22DABF.1020807@anonymous.org.uk> (raw)
In-Reply-To: <20110717122230.GB2614@teal.hq.k1024.org>

On 17/07/2011 13:22, Iustin Pop wrote:
> On Sun, Jul 17, 2011 at 01:11:19PM +0100, John Robinson wrote:
[...]
>> # dd if=/dev/zero of=test bs=4096 count=262144
>> 262144+0 records in
>> 262144+0 records out
>> 1073741824 bytes (1.1 GB) copied, 2.5253 seconds, 425 MB/s
>>
>> And there's a badblocks running on another drive also on the ICH10.
>>
>> Having said that, I think mine's wrong too, I don't think my array
>> can really manage that much throughput. We should both be using more
>> realistic benchmarking tools like bonnie++:
>
> Or simply pass the correct flags to dd — like oflag=direct, which will
> make it do non-buffered writes.

That's still not realistic:

# dd if=/dev/zero of=test oflag=direct bs=4096 count=262144
262144+0 records in
262144+0 records out
1073741824 bytes (1.1 GB) copied, 117.434 seconds, 9.1 MB/s

Because this time we're doing a read-modify-write for every 4K block, or 
at least a write for every 4K block. I can fix it up again to work in 
stripe size amounts:

# dd if=/dev/zero of=test oflag=direct bs=1572864 count=683
683+0 records in
683+0 records out
1074266112 bytes (1.1 GB) copied, 18.3198 seconds, 58.6 MB/s

But it's still not realistic because real I/O does use buffers and 
doesn't work in magic sizes, so we should be using a more realistic 
benchmarking tool like bonnie++.

Cheers,

John.

--
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:[~2011-07-17 12:51 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-16 19:40 standard performance (write speed 20Mb/s) Pol Hallen
2011-07-17  4:26 ` Stan Hoeppner
2011-07-17  8:12   ` Pol Hallen
2011-07-17 12:11     ` John Robinson
2011-07-17 12:22       ` Iustin Pop
2011-07-17 12:51         ` John Robinson [this message]
2011-07-17 13:28           ` Iustin Pop
2011-07-18  9:04             ` John Robinson
2011-07-17 22:05         ` Stan Hoeppner
2011-07-27  5:42       ` Simon Matthews
2011-07-27  5:46         ` Roman Mamedov
2011-07-27 10:22         ` Stan Hoeppner
2011-07-27 10:26           ` John Robinson
2011-07-27 12:35             ` Joe Landman
2011-07-27 13:54             ` Stan Hoeppner
2011-07-17 23:03     ` Stan Hoeppner
2011-07-18 11:52       ` Pol Hallen
2011-07-21 17:07       ` standard performance (write speed ??Mb/s) - new raid5 array Pol Hallen
2011-07-22  0:05         ` Stan Hoeppner
2011-07-22  7:08           ` Pol Hallen
2011-07-22  8:13             ` Erwan Leroux
2011-07-17 16:48 ` standard performance (write speed 20Mb/s) Gordon Henderson
  -- strict thread matches above, loose matches on Subject: below --
2011-07-18 12:03 Pol Hallen
2011-07-20 12:31 ` Stan Hoeppner
2011-07-20 20:02   ` Pol Hallen
     [not found]     ` <CADNH=7HR7euaWem0tpLxJfRe0hYnRP5fwxJ6MC5vJeNf=T=PzA@mail.gmail.com>
2011-07-21  0:02       ` Stan Hoeppner
2011-07-21  6:57         ` Mathias Burén
2011-07-21  8:55     ` Erwan Leroux
2011-07-21 15:06       ` Paweł Brodacki
2011-07-21 15:30         ` Erwan Leroux
2011-07-21 15:42           ` Erwan Leroux
2011-07-25  6:39             ` Paweł Brodacki

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=4E22DABF.1020807@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=iusty@k1024.org \
    --cc=linux-raid@vger.kernel.org \
    /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.