From: Ben Myers <bpm@sgi.com>
To: Erik Knight <kutuzof@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: dozens of xfsaild threads
Date: Fri, 22 Feb 2013 14:25:18 -0600 [thread overview]
Message-ID: <20130222202518.GX22182@sgi.com> (raw)
In-Reply-To: <CAGot=x-aiATNxBty7FXxV_td7Wx1_Mh8c8ta=mr4hpHxtmv6Nw@mail.gmail.com>
Hi Erik,
On Fri, Feb 22, 2013 at 02:04:17PM +0100, Erik Knight wrote:
> We've recently noticed that our system is experiencing extreme performance
> problems when running large workloads. The problem seems to come from
> excessive System CPU time. Specifically dozens of xfsaild threads. We used
> to have SSD drives but recently switched to HDD, so some of us are thinking
> that there may be a configuration issue within XFS that is optimized for
> SSD but performs terribly slow on HDD.
>
> Can anyone explain what these threads do, what would cause so many of them
> to be running simultaneously or consume so much CPU?
AIL stands for Active Item List. These guys sync metadata which has been
logged to its final location on disk. You'll have one daemon per filesystem.
If you have a very metadata intensive workload they could get a workout. It
would help to know a bit more about your workload and configuration. Can you
provide the relevant information listed here?
http://www.xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
Regards,
Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-02-22 20:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 13:04 dozens of xfsaild threads Erik Knight
2013-02-22 20:25 ` Ben Myers [this message]
2013-02-22 23:27 ` Erik Knight
2013-02-24 11:13 ` Erik Knight
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=20130222202518.GX22182@sgi.com \
--to=bpm@sgi.com \
--cc=kutuzof@gmail.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