From: Dave Chinner <david@fromorbit.com>
To: Michael Spiegle <mike@nauticaltech.com>
Cc: xfs@oss.sgi.com
Subject: Re: 1B files, slow file creation, only AG0 used
Date: Mon, 12 Mar 2012 11:56:32 +1100 [thread overview]
Message-ID: <20120312005632.GY5091@dastard> (raw)
In-Reply-To: <CAEm1Pvny7Q2rrsCLURvo5kQM3vt+yMg17WxoSYGKVWm7Lgp8MA@mail.gmail.com>
On Fri, Mar 09, 2012 at 06:13:27PM -0800, Michael Spiegle wrote:
> We're seeing some very strange behavior with XFS on the default kernel
> for CentOS 5.6 (note, I have also 3.2.9 and witnessed the same issue).
> The dataset on this server is about 1B small files (anywhere from 1KB
> to 50KB). We first noticed it when creating files in a directory. A
> simple 'touch' would take over 300ms on a completely idle system. If
> I simply create a different directory, touching files is 1ms or
> faster. Example:
>
> # time touch 0
> real 0m0.323s
> user 0m0.000s
> sys 0m0.323s
>
> # mkdir tmp2
> # time touch tmp2/0
> real 0m0.001s
> user 0m0.000s
> sys 0m0.000s
Entirely normal. some operations require Io to complete (e.g.
reading directory blocks to find where to insert the new entry),
while adding the first file to a directory generally requires zero
IO. You're seeing the difference between cold cache and hot cache
performance.
> We've done quite a bit of testing and debugging, and while we don't
> have an answer yet, we've noticed that our filesystem was created with
> the default of 32 AGs. When using xfs_db, we notice that all
> allocations appear to be in AG0 only.
Go look up what the inode32 and inode64 mount options do. The
default is inode32....
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:[~2012-03-12 0:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 2:13 1B files, slow file creation, only AG0 used Michael Spiegle
2012-03-10 4:59 ` Eric Sandeen
2012-03-10 5:25 ` Michael Spiegle
2012-03-12 2:59 ` Stan Hoeppner
2012-03-12 22:11 ` Michael Spiegle
2012-03-12 0:56 ` Dave Chinner [this message]
2012-03-12 21:54 ` Michael Spiegle
2012-03-13 0:08 ` Dave Chinner
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=20120312005632.GY5091@dastard \
--to=david@fromorbit.com \
--cc=mike@nauticaltech.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