From: Dave Chinner <david@fromorbit.com>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: xfs@oss.sgi.com
Subject: Re: deleting 2TB lots of files with delaylog: sync helps?
Date: Wed, 1 Sep 2010 13:41:56 +1000 [thread overview]
Message-ID: <20100901034156.GQ705@dastard> (raw)
In-Reply-To: <4C7DC21B.1040705@hardwarefreak.com>
On Tue, Aug 31, 2010 at 10:01:47PM -0500, Stan Hoeppner wrote:
> Dave Chinner put forth on 8/31/2010 7:06 PM:
>
> > You're probably CPU bound, not IO bound.
>
> 7200 rpm is the highest spindle speed for 2TB drives--5400 is most
> common. None of them are going to do much over 200 random seeks/second,
> if that. That's 400 tops for two drives.
>
> Using any modern Intel/AMD ~2 GHz CPU, you think he's CPU bound?
Absolutely.
> Apparently this "rm -rf" type operation is much more complex than I
> previously believed.
Nothing in XFS is simple. ;)
Unlinks that free the inode clusters results in no inode writeback
load, so the majority of the IO is log traffic. Hence they are
either log IO bound or read latency bound. A pair of 2TB SATA
drives will be good for at least 150MB/s of log throughput, but
the numbers are nowhere near that.
Without delayed logging, 150MB/s is enough for a single threaded
unlink to consume an entire CPU core on any modern CPU, and there
maybe enough bandwidth for two threads to max out 2 CPUs. With
delaylog, log throughput is reduced by an order of magnitude, so
should be good for at least 10x that number of CPU cores running
flat out unless they are latency bound reading the directories
and inodes into memory.....
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:[~2010-09-01 3:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 23:30 deleting 2TB lots of files with delaylog: sync helps? Michael Monnerie
2010-09-01 0:06 ` Dave Chinner
2010-09-01 0:22 ` Michael Monnerie
2010-09-01 3:19 ` Dave Chinner
2010-09-01 4:42 ` Stan Hoeppner
2010-09-01 6:44 ` Dave Chinner
2010-09-02 5:37 ` Stan Hoeppner
2010-09-02 7:01 ` Dave Chinner
2010-09-02 8:41 ` Stan Hoeppner
2010-09-02 11:29 ` Dave Chinner
2010-09-02 14:57 ` Stan Hoeppner
2010-09-01 3:01 ` Stan Hoeppner
2010-09-01 3:41 ` Dave Chinner [this message]
2010-09-01 7:45 ` Michael Monnerie
2010-09-02 1:17 ` Dave Chinner
2010-09-02 2:15 ` Michael Monnerie
2010-09-02 7:51 ` Stan Hoeppner
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=20100901034156.GQ705@dastard \
--to=david@fromorbit.com \
--cc=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