All of lore.kernel.org
 help / color / mirror / Atom feed
From: "spren.gm@gmail.com" <spren.gm@gmail.com>
To: dong wu <dongwucs@gmail.com>,
	"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: why is md/raid5 sequential write speed so slow?
Date: Fri, 8 Jan 2010 13:39:21 +0800	[thread overview]
Message-ID: <201001081339187349051@gmail.com> (raw)
In-Reply-To: 6c394cc31001072119l2619d8aap627164d34eec6806@mail.gmail.com

> from:dong wu
>I have made a test in my server!
>raid5 capacity:80G,  disks:9
>IO type                        IOPS                   speed(M/s)
>1024k seq write            40.67                   40.67
>512k seq write              70.89                   39.45
>256k seq write             36.02                    34.00
>128k seq write             134.19                   16.77
>64k seq write               232.26                   14.52
>32k seq write              160.23                    5.01
>16k seq write              148.48                    2.32
>8k seq write                151.05                   1.18
>4k seq write                151.39                   0.59
>2k seq write                 290.90                  0.57
>1k seq write                 526.21                  0.51
>512B seq write             1076.60                0.53
>
>I don't know why raid5 seq write is so slow.
>Does delaying write cause this?
>
well, 
(1) is raid5 degraded ,recovering or resyncing ?
(2) how is the speed of members ?
(3) how do you test that (tools) and how is the cpu utilization during test?
(4) it seems that you used partitions of disks as raid members, any other read/write operations on other partitions ?
(5) try to set /sys/block/mdX/md/stripe_cache_size larger
(6) XOR calculation too slow?

------------------				 
spren.gm@gmail.com
2010-01-08



      reply	other threads:[~2010-01-08  5:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-08  5:19 why is md/raid5 sequential write speed so slow? dong wu
2010-01-08  5:39 ` spren.gm [this message]

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=201001081339187349051@gmail.com \
    --to=spren.gm@gmail.com \
    --cc=dongwucs@gmail.com \
    --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.