linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.ru>
To: Simon Matthews <simon.d.matthews@gmail.com>
Cc: John Robinson <john.robinson@anonymous.org.uk>,
	Pol Hallen <raid1@fuckaround.org>,
	linux-raid@vger.kernel.org
Subject: Re: standard performance (write speed 20Mb/s)
Date: Wed, 27 Jul 2011 11:46:47 +0600	[thread overview]
Message-ID: <20110727114647.5a80b3d0@natsu> (raw)
In-Reply-To: <CAEUYfyMEj31Gfy9KeT4sHWyUXcB-+9ehoZoXvHSXq6yztCzVXg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 789 bytes --]

On Tue, 26 Jul 2011 22:42:14 -0700
Simon Matthews <simon.d.matthews@gmail.com> wrote:

> On Sun, Jul 17, 2011 at 5:11 AM, John Robinson
> <john.robinson@anonymous.org.uk> wrote:
> 
> > 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
> 
> What hard drive offers a sustained data rate of 425 MB/s or even half that?

"md RAID 6 over 5 7200rpm 1TB drives" does? :) At least half that - easily.

But still, the result posted is very much inflated, they forgot the "conv=fdatasync" option, so mostly benchmarking the FS cache in RAM.

-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-07-27  5:46 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
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 [this message]
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=20110727114647.5a80b3d0@natsu \
    --to=rm@romanrm.ru \
    --cc=john.robinson@anonymous.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=raid1@fuckaround.org \
    --cc=simon.d.matthews@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).