From: Stan Hoeppner <stan@hardwarefreak.com>
To: mark delfman <markdelfman@googlemail.com>
Cc: Linux RAID Mailing List <linux-raid@vger.kernel.org>,
NeilBrown <neilb@suse.de>
Subject: Re: single cpu thread performance limit?
Date: Fri, 12 Aug 2011 15:51:30 -0500 [thread overview]
Message-ID: <4E459252.7060700@hardwarefreak.com> (raw)
In-Reply-To: <CAACGR8v87iw9qmtfsQTiUP8QWQEZPyryBc_zZwuD_DyUxgzN8Q@mail.gmail.com>
On 8/12/2011 8:23 AM, mark delfman wrote:
> Quick update with the XFS tests suggested (although a FS is still
> probably not a real option at teh moment for me)
>
> This rig only has 4 x Flash (2 MLC and 2 SLC)..... 125K IOPS each for
> MLC - 165K each for SLC.
>
> Create linear RAID and XFS with ag=4
>
> Mount as suggested and create 4 test folders.....
>
> If i test individually - we get 99.9% of the IOPS (ie. 125 for first 2
> AG's and 165 for last 2). which is great news and means that the AG
> does what it should.
Now you know why XFS has the high performance reputation it does.
> But if a run the test over all 4, then we see it peak at aroudn 320K
> IOPS. Interstingly each AG = 80K IOPS and as we can see above this is
> need not be the case, as the CPU load is not having any issues - i am
> presuming that this could be a simple XFS limit maybe.
Ok, now this is interesting, because the 320K IOPS you mentioned as a
limit here is very close to the ~350K IOPS you mentioned in your first
post, when 4 cores were pegged with the md processes. In this case your
CPUs are not pegged, but you're hitting nearly the same ceiling, 320K IOPS.
I'm pretty sure you're not hitting an XFS limit here. To confirm,
create 4 subdirectories in each of the current 4 directories, and
generate 16 concurrent writers against the 16 dirs.
On 8/11/2011 10:58 AM, mark delfman wrote:
> If I use say 4 x RAID1 / 10’s and a RAID0 on top – I see not much
> greater results. (although the theory seems to say I should and there
> are now 4 CPU threads running, it still seems to hit 4 x 100% at maybe
> 350K).
So it's beginning to look like your scalability issue may not
necessarily be with mdraid, but possibly a hardware bottleneck, or a
bottleneck somewhere else in the kernel. As Bernd mentioned previously,
you should probably run perf top or some other tool to see where the
kernel is busy.
Also, you never answered my question regarding which block device
driver(s) you're using for these PCIe SSDs.
> More testing with many R1's and R0's on top seem to suggest that R0 is
> losing around 20-25% of the IOPS. (R1 around 5%). I have tried with
> LVM strip and much the same.
Are you hitting the same ~320K-350K IOPS aggregate limit with all test
configurations?
--
Stan
--
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
next prev parent reply other threads:[~2011-08-12 20:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 15:58 single cpu thread performance limit? mark delfman
2011-08-11 16:01 ` Mathias Burén
2011-08-11 16:07 ` mark delfman
2011-08-11 18:58 ` Stan Hoeppner
2011-08-11 19:37 ` mark delfman
2011-08-11 19:57 ` Joe Landman
2011-08-12 9:04 ` David Brown
2011-08-11 20:51 ` Stan Hoeppner
2011-08-12 1:05 ` Stan Hoeppner
2011-08-12 12:48 ` Asdo
2011-08-12 13:23 ` mark delfman
2011-08-12 14:23 ` Asdo
2011-08-12 20:51 ` Stan Hoeppner [this message]
2011-08-11 19:04 ` Bernd Schubert
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=4E459252.7060700@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=linux-raid@vger.kernel.org \
--cc=markdelfman@googlemail.com \
--cc=neilb@suse.de \
/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