linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jaap Crezee <jaap@jcz.nl>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: "Jeff Moyer" <jmoyer@redhat.com>,
	"Rogier Wolff" <R.E.Wolff@bitwizard.nl>,
	"Bruno Prémont" <bonbons@linux-vserver.org>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Slow disks.
Date: Thu, 23 Dec 2010 20:10:38 +0100	[thread overview]
Message-ID: <4D139EAE.9090307@jcz.nl> (raw)
In-Reply-To: <AANLkTikbhzopmyfbJuHUQdEBJLLP9e65n0cNBuUjhDdd@mail.gmail.com>

On 12/23/10 19:51, Greg Freemyer wrote:
 > On Thu, Dec 23, 2010 at 12:47 PM, Jeff Moyer<jmoyer@redhat.com>  wrote:
 > I suspect a mailserver on a raid 5 with large chunksize could be a lot
 > worse than 2x slower.  But most of the blame is just raid 5.

Hmmm, well if this really is so.. I use raid 5 to not "spoil" the storage space 
of one disk. I am using some other servers with raid 5 md's which seems to be 
running just fine; even under higher load than the machine we are talking about.

Looking at the vmstat block io the typical load (both write and read) seems to 
be less than 20 blocks per second. Will this drop the performance of the array 
(measured by dd if=/dev/md<x> of=/dev/null bs=1M) below 3MB/secs?

 > ie.
 > write 4K from userspace
 >
 > Kernel
 > Read old primary data, wait for data to actually arrive
 > Read old parity data, wait again
 > modify both for new data
 > write primary data to drive queue
 > write parity data to drive queue

What if I (theoratically) change the chunksize to 4kb? (I can try that in the 
new server...).

Jaap

  reply	other threads:[~2010-12-23 19:10 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20101220141553.GA6088@bitwizard.nl>
2010-12-20 18:06 ` Slow disks Bruno Prémont
2010-12-20 18:32   ` Greg Freemyer
2010-12-22 10:43     ` Rogier Wolff
2010-12-22 15:59       ` Greg Freemyer
2010-12-22 16:27       ` Jeff Moyer
2010-12-22 22:44         ` Rogier Wolff
2010-12-23 14:40           ` Jeff Moyer
2010-12-23 17:01             ` Rogier Wolff
2010-12-23 17:47               ` Jeff Moyer
2010-12-23 18:51                 ` Greg Freemyer
2010-12-23 19:10                   ` Jaap Crezee [this message]
2010-12-23 22:09                     ` Greg Freemyer
2010-12-24 11:40                       ` Rogier Wolff
2010-12-26 23:05                         ` Greg Freemyer
2010-12-27  0:27                           ` Rogier Wolff
2010-12-27  7:21                             ` Stan Hoeppner
2010-12-24 10:45                 ` Rogier Wolff
2010-12-26 23:38         ` Mark Knecht
2010-12-27  0:34           ` Rogier Wolff
2010-12-27  3:12             ` Mark Knecht
2010-12-27 18:20           ` Krzysztof Halasa
2010-12-24 13:01       ` Krzysztof Halasa
2010-12-24 15:24         ` Michael Tokarev
2010-12-24 20:58           ` Krzysztof Halasa
2010-12-25 12:14           ` Rogier Wolff
2010-12-25 12:19             ` Mikael Abrahamsson
2010-12-26 21:40             ` Rogier Wolff
2010-12-26 23:17               ` Greg Freemyer
2010-12-26 23:49                 ` Rogier Wolff

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=4D139EAE.9090307@jcz.nl \
    --to=jaap@jcz.nl \
    --cc=R.E.Wolff@bitwizard.nl \
    --cc=bonbons@linux-vserver.org \
    --cc=greg.freemyer@gmail.com \
    --cc=jmoyer@redhat.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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 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).