linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Manish Awasthi <manish.awasthi@caviumnetworks.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: md raid performance with 3-18-rc3
Date: Wed, 3 Dec 2014 16:19:54 +1100	[thread overview]
Message-ID: <20141203161954.2515740d@notabene.brown> (raw)
In-Reply-To: <54758B3B.5080907@caviumnetworks.com>

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

On Wed, 26 Nov 2014 13:41:39 +0530 Manish Awasthi
<manish.awasthi@caviumnetworks.com> wrote:

> 
> On 11/25/2014 08:07 AM, NeilBrown wrote:
> > On Mon, 24 Nov 2014 13:40:06 +0530 Manish Awasthi
> > <manish.awasthi@caviumnetworks.com> wrote:
> >
> >> Hi,
> >>
> >> We benchmarked the md raid driver performance on 3-18-rc3 kernel and
> >> compared the results with that of 3.6.11. The reason for this exercise
> >> is to understand if multithreaded raid driver has any performance
> >> benefits over 3.6.11 which is single threaded. Here are some details
> >> about the setup
> > Thanks for doing this!!!! I love it when people report test results.
> >
> >
> >> System: Intel(R) Xeon(R) CPU E3-1230 V2 @ 3.30GHz 4 cores (8threads),
> >> 8GB RAM.
> >> Setup: 3 SSDs create a raid5 array
> >> test tool: iozone (only read/re-read, write/re-write tested), blocksize:
> >> 4k-64k, filesize: 1Gig to 200Gig
> >>
> >> Comparison was done for speed of data transfer in kBytes/sec and also
> >> the CPU utilization as reported by iozone.
> >>
> >> raid on 3.18.0-rc3 performed much worse than raid on 3.6.11.
> >>
> >> Read/Write: raid on 3.18.0-rc3 operated at almost half the speed of raid
> >> on 3.6.11
> > That really isn't very good.... Can you try some of the kernels in between
> > and see if there was a single point where performance dropped, or if there
> > were several steps?
> Can you give me some starting point when multithread support for raid 
> was added. It might be a good starting point. For instance, I have a 
> benchmark on 3.6.11, now I'd like to go to the first kernel that has 
> support for multithread raid and then take it from there.

Multi-thread support appeared in 3.12.


> >
> >
> >> CPU Utilization: With md raid on 3.18.0-rc3, the CPU utilization was
> >> less than half of md raid on 3.6.11 on WRITE operations. However, for
> >> READ operations, 3.18-0.rc3 had more CPU utilization than 3.6.11.
> > Can you use "perf" to determine where the extra time is going?
> >
> >    perf record
> >    run test
> >    stop perf
> >    perf report
> >
> > or something like that.
> I can do this but as I mentioned below, Its better if I can get to 
> understand all the possible tweaks that can be done to get the optimal 
> results unless ofcourse you expect 3.18.0 to perform better than that of 
> 3.6.11 even if default case without any tweaks.

I have no particular expectations.  I like to see concrete measurements and
then try to interpret them.

I prefer to compare default setting (no tweaks) in the first instance.
Because that is what most people will be using.


> >
> >> Also, I noticed that scaling up the CPU cores of the system scales down
> >> the raid througput with 3.18.0-rc3.
> > This is by writing numbers to "group_thread_cnt" ??? Can you provide a simple
> > table comparing thread count to throughput?  Or maybe a graph.  I love
> > graphs :-)
> I did not tweak anything on the 3.18.0 kernel. I assumed all the 
> required support is built-in and did not bother to go into the depth of 
> the code as we're still in nascent stages where we are comparing the 
> data on specific kernel versions. Can you point me to some text that can 
> describe tweaks like "group_thread_cnt" etc?

Multi-threading is disabled by default, so if you haven't explicitly enabled
it, then it cannot be affecting your performance.

If you
  echo 8 > /sys/block/mdXXX/md/group_thread_cnt

it will use 8 thread to perform 'xor' calculations and submit IO requests.


> >
> >> I do have detailed logs of the comparison but I'm not sure I should send
> >> those on this mailing list.
> > A few megabytes?  Yes.  100Meg?  No.
> 
> Whatever data I have on comparison is attached, I have consolidated this 
> from log files to excel. See if this helps.

Thanks.  I'll have a look at the tables and see if anything looks interesting.

Thanks,
NeilBrown



> >
> > If you could put them on a website somewhere that I can browse or download
> > I'll try to have a look.
> >
> >> If my observation aligns with someone else's, then what is really the
> >> gain with multithreaded raid.
> > Some testing shows real improvements.  Obviously we cannot test everything
> > and I'm very glad to have extra testing from other people.
> > If we can quantify the regressions and confirm exactly when they occurred, we
> > can start looking for a solution.
> >
> > Thanks a lot!
> >
> > NeilBrown
> >
> >
> >> Manish
> >> --
> >> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> >> the body of a message to majordomo@vger.kernel.org
> >> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

  parent reply	other threads:[~2014-12-03  5:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24  8:10 md raid performance with 3-18-rc3 Manish Awasthi
2014-11-25  2:37 ` NeilBrown
     [not found]   ` <54758B3B.5080907@caviumnetworks.com>
2014-12-03  5:19     ` NeilBrown [this message]
2014-12-03  6:21     ` NeilBrown
     [not found]       ` <5486B15C.8060109@caviumnetworks.com>
2014-12-09  8:24         ` Manish Awasthi
2014-12-09  8:26           ` Manish Awasthi
     [not found]             ` <5487FD79.7000002@caviumnetworks.com>
2015-01-06  9:49               ` Manish Awasthi
2015-01-07 10:52                 ` Manish Awasthi

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=20141203161954.2515740d@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=manish.awasthi@caviumnetworks.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).