Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Neil Brown <nfbrown@novell.com>
To: Marco <jjletho67-diar@yahoo.it>
Cc: Roman Mamedov <roman@rm.pp.ru>, linux-raid@vger.kernel.org
Subject: Re: raid1 performance
Date: Wed, 28 Jul 2010 08:23:58 +1000	[thread overview]
Message-ID: <20100728082358.4abc6868@notabene> (raw)
In-Reply-To: <379853.84515.qm@web28502.mail.ukl.yahoo.com>

On Tue, 27 Jul 2010 16:10:36 +0000 (GMT)
Marco <jjletho67-diar@yahoo.it> wrote:

> 
> 
> 
> 
> >If you look at /proc/diskstats and particularly the 4th and 6th fields for
> >the device that you are interested in, and then take the differences for each
> >field between 'before' and 'after' running a test you will get
> > - the number of IO requests
> >  - the number of sectors
> >
> >that were serviced during that time.  Taking a ratio will get you the number
> >of sectors per IO.  Normally more is better.
> 
> Hi Neil,
> are you sure the right value are the 4th and the 6th fields ? I see strange 
> value in them (the 4th field is bigger then the 6th while i was expecting the 
> contrary)
> looking in the iostats.txt file (kernel documentation) i suspect the fields you 
> are interested are the first and the third.

No, the first field is the major device number, and the third is the device
name ....
so I guess we are taking the same ratio, but you start counting at a
different place to me.

> In this hypothesis (1st and 3rd fields) the ratio i obtain are:
> 
> sda 84.02 
> sdb 113,69
> md2 8,01
> 
> md2 and his meber have a very different ratio....

Strange isn't it.  And the ratios are the other-way-around to what I get.
I don't currently understand why ... but it might not be at all relevant to
the speed difference.

> 
> >It might be interesting to find out what the data offset is for your RAID1
> >(mdadm --examine will tell you if there is one), and compare the
> > request/sector numbers and see if they show anything.
> 
> this is the output of mdadm --examine /dev/sda3
> 
> /dev/sda3:
>           Magic : a92b4efc
>         Version : 0.90.00

OK, so there is no data offset with 0.90, so that rules out differing offsets
being an issue.

> 
> Do you have some hypothesis ?

No.  It might be worth exploring why the request sizes are different - I
don't know if it will lead anywhere useful though.

NeilBrown

> 
> thank you all
> 
> Marco
> 
> 
> 
>       


  reply	other threads:[~2010-07-27 22:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-25 14:58 raid1 performance Marco
2010-07-25 15:19 ` Roman Mamedov
2010-07-26  9:37   ` Marco
2010-07-26 10:24     ` Keld Simonsen
2010-07-26 10:53       ` John Robinson
2010-07-26 11:30         ` Keld Simonsen
2010-07-27 16:10       ` Marco
2010-07-26 11:03     ` Neil Brown
2010-07-27  1:23       ` Leslie Rhorer
2010-07-27 16:10       ` Marco
2010-07-27 22:23         ` Neil Brown [this message]
2010-07-28 12:10           ` Marco
2010-07-28 12:24             ` Neil Brown
2010-07-31 15:21           ` Marco
2010-07-31 16:04             ` Keld Simonsen
  -- strict thread matches above, loose matches on Subject: below --
2010-07-19 12:14 Marco
2004-04-21  5:57 RAID1: Performance Mike Mestnik

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=20100728082358.4abc6868@notabene \
    --to=nfbrown@novell.com \
    --cc=jjletho67-diar@yahoo.it \
    --cc=linux-raid@vger.kernel.org \
    --cc=roman@rm.pp.ru \
    /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