From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: XFS: performance
Date: Tue, 30 Nov 2010 18:47:39 -0600 [thread overview]
Message-ID: <4CF59B2B.80701@hardwarefreak.com> (raw)
In-Reply-To: <20101130075109.GN13830@dastard>
Dave Chinner put forth on 11/30/2010 1:51 AM:
> No, it detected the RAID configuration. 16 AGs is the default for a
> RAID device, 4 AGs is used if RAID is not detected.
So, as a general rule of thumb, one should have as many AGs as the
maximum number of potential writers, assuming the underlying storage
device can handle the I/O? For instance, on a quad socket 12 core Magny
Cours system with 48 total cores, if one has an application with 48
writing threads, one should have at least 48 AGs?
And if the the default is 4 AGs per physical disk, does this mean one
should have at least 12 drives in the stripe width? I'm thinking of
SRDs in my example, not SSDs. And obviously if these are heavy writing
threads, a single 2 GHz core can easily outrun a single disk, so one
would probably want at least 48 SRDs if not 96 in the stripe. Yes?
Obviously there are potentially many other factors that may come into
play in this equation. I'm just looking for a general formula one
should use as a baseline template, as 16 AGs doesn't seem to be enough
for any application, core/thread count, SRD RAID configuration.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-12-01 0:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-28 22:51 XFS: performance Yclept Nemo
2010-11-29 0:11 ` Dave Chinner
2010-11-29 1:21 ` Yclept Nemo
2010-11-29 1:59 ` Dave Chinner
[not found] ` <AANLkTikw086Z_66cz_U-EdFQx14TXP6XmiG-KyLN4BLo@mail.gmail.com>
2010-11-29 3:57 ` Yclept Nemo
2010-11-29 5:41 ` Stan Hoeppner
2010-11-30 4:29 ` Dave Chinner
2010-11-30 4:50 ` Stan Hoeppner
2010-11-30 7:51 ` Dave Chinner
2010-12-01 0:47 ` Stan Hoeppner [this message]
2010-11-29 8:38 ` Michael Monnerie
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=4CF59B2B.80701@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=xfs@oss.sgi.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