From: Stan Hoeppner <stan@hardwarefreak.com>
To: Pol Hallen <raid1@fuckaround.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: standard performance (write speed 20Mb/s)
Date: Sat, 16 Jul 2011 23:26:12 -0500 [thread overview]
Message-ID: <4E226464.2030200@hardwarefreak.com> (raw)
In-Reply-To: <201107162140.58883.raid1@fuckaround.org>
On 7/16/2011 2:40 PM, Pol Hallen wrote:
> Hi folks :-)
>
> after assembled a new hw (xeon, ich10 controller with 5 disks of 2Tb wd -
> radi5) I have slow write performance:
>
> 20Mb/s :-(((
>
> dd if=/dev/zero of=/share/raid/1Gb bs=1024M count=1
> 1+0 records in
> 1+0 records out
> 1073741824 bytes (1.1 GB) copied, 48.7203 s, 22.0 MB/s
Using a write block size of 1GB with dd causes the entire file to be
buffered to RAM before being flushed to disk. To prove the point, I
just ran your test against a single SATA disk with an XFS filesystem.
XFS is is optimized for large files.
$ dd if=/dev/zero of=./test bs=1024M count=1
1+0 records in
1+0 records out
1073741824 bytes (1.1 GB) copied, 139.895 s, 7.7 MB/s
The same test using a *sane* block size of 4KB:
$ dd if=/dev/zero of=./test bs=4096 count=262144
262144+0 records in
262144+0 records out
1073741824 bytes (1.1 GB) copied, 15.0732 s, 71.2 MB/s
10x decrease in performance due to the insane 1GB block size.
The machine I ran this test on is old, having only 384MB RAM and a
Sil3512 PCI SATA-I controller. The disk is a WD Blue 500GB 7.2K. Using
the 1GB block size ate over 800MB of swap out of 1GB before the buffer
was flushed. This massive buffering is what murders performance here.
Repeat your test using a 4KB block size and post the results.
Know your tools Pol.
--
Stan
next prev parent reply other threads:[~2011-07-17 4:26 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 [this message]
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
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=4E226464.2030200@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--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).