From: Dave Chinner <david@fromorbit.com>
To: Radoslaw Garbacz <radoslaw.garbacz@xtremedatainc.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs - high CPU usage when removing files
Date: Tue, 14 May 2013 10:47:51 +1000 [thread overview]
Message-ID: <20130514004751.GQ32675@dastard> (raw)
In-Reply-To: <CAHBw7oSxcTYEEFzzhpZfH_EshyYXOsRBpf=S+bLEgCyQZkLFsA@mail.gmail.com>
On Mon, May 13, 2013 at 01:28:47PM -0500, Radoslaw Garbacz wrote:
> Hi,
>
> I noticed a high CPU usage when removing files from XFS partition on Linux,
> CentOS (always close to 100%).
> Is it a known issue, or is it more likely to be attributed to my testing
> methodology ('time' command)?
If you are removing extremely fragmented files, then 100% CPU will
be seen. If you are removing tens of thousands of small files, then
100% CPU will be seen,
IOWs, if there's enough work to be done, removing files will use all
the available CPU. There's no problem with that.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-05-14 0:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 18:28 xfs - high CPU usage when removing files Radoslaw Garbacz
2013-05-14 0:47 ` Dave Chinner [this message]
2013-05-14 11:11 ` Stefan Ring
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=20130514004751.GQ32675@dastard \
--to=david@fromorbit.com \
--cc=radoslaw.garbacz@xtremedatainc.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