From: John Robinson <john.robinson@anonymous.org.uk>
To: Pol Hallen <raid1@fuckaround.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: standard performance (write speed 20Mb/s)
Date: Sun, 17 Jul 2011 13:11:19 +0100 [thread overview]
Message-ID: <4E22D167.2010905@anonymous.org.uk> (raw)
In-Reply-To: <ac6850f9420970de26472b6a9dcc2a82.squirrel@fuckaround.org>
On 17/07/2011 09:12, Pol Hallen wrote:
> hello and thanks for the reply :-)
>
> dd if=/dev/zero of=test bs=4096 count=262144
> 262144+0 records in
> 262144+0 records out
> 1073741824 bytes (1.1 GB) copied, 31.3475 s, 34.3 MB/s
Pretty poor. CentOS 5, Intel ICH10, md RAID 6 over 5 7200rpm 1TB drives,
then LVM, then ext3:
# 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++:
Version 1.03 ------Sequential Output------ --Sequential Input-
--Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block--
--Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP
/sec %CP
beast.private.yu 7G 80890 91 67527 13 41608 4 74028 69 205104 9
378.7 0
------Sequential Create------ --------Random
Create--------
-Create-- --Read--- -Delete-- -Create-- --Read---
-Delete--
files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
/sec %CP
16 +++++ +++ +++++ +++ +++++ +++ +++++ +++ +++++ +++
+++++ +++
beast.private.yuiop.co.uk,7G,80890,91,67527,13,41608,4,74028,69,205104,9,378.7,0,16,+++++,+++,+++++,+++,+++++,+++,+++++,+++,+++++,+++,+++++,+++
And I should think of a command line options so I don't get all those +
signs. Never mind, the above shows 40-80MB/s for writes, 70-200MB/s for
reads, which is not too bad even if it's not great.
Hang on. You aren't trying to benchmark your array just after creating
it, while it's still doing its initial sync, are you?
Cheers,
John.
next prev parent reply other threads:[~2011-07-17 12:11 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 [this message]
2011-07-17 12:22 ` Iustin Pop
2011-07-17 12:51 ` John Robinson
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=4E22D167.2010905@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=raid1@fuckaround.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 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).