From: Christoph Hellwig <hch@infradead.org>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs@oss.sgi.com
Subject: Re: LWN.net article: creating 1 billion files -> XFS looses
Date: Thu, 19 Aug 2010 08:05:12 -0400 [thread overview]
Message-ID: <20100819120512.GB9358@infradead.org> (raw)
In-Reply-To: <201008191312.49346@zmi.at>
On Thu, Aug 19, 2010 at 01:12:45PM +0200, Michael Monnerie wrote:
> The subject is a bit harsh, but overall the article says:
> XFS is slowest on creating and deleting a billion files
> XFS fsck needs 30GB RAM to fsck that 100TB filesystem.
>
> http://lwn.net/SubscriberLink/400629/3fb4bc34d6223b32/
The creation and deletion performance is a known issue, and too a large
extent fixes by the new delaylog code. We're not quite as fast as ext4
yet, but it's getting close.
The repair result looks a lot like the pre-3.1.0 xfsprogs repair.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-08-19 12:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 11:12 LWN.net article: creating 1 billion files -> XFS looses Michael Monnerie
2010-08-19 12:05 ` Christoph Hellwig [this message]
2010-08-19 12:45 ` Michael Monnerie
2010-08-19 13:55 ` Stan Hoeppner
2010-08-20 7:55 ` Dave Chinner
2010-08-19 13:10 ` Emmanuel Florac
2010-09-06 13:42 ` Emmanuel Florac
2010-09-06 22:04 ` Dave Chinner
2010-09-06 22:58 ` Michael Monnerie
2010-09-07 3:31 ` Dave Chinner
2010-09-07 6:20 ` Michael Monnerie
2010-09-07 7:01 ` Dave Chinner
2010-09-08 5:42 ` Michael Monnerie
2010-09-07 6:46 ` Emmanuel Florac
2010-09-16 10:13 ` LWN.net article: creating 1 billion files -> Tests we did Emmanuel Florac
2010-09-16 21:53 ` Stan Hoeppner
2010-09-17 7:54 ` Michael Monnerie
2010-09-17 19:29 ` Peter Grandi
2010-09-18 11:25 ` Emmanuel Florac
2010-09-18 11:16 ` Emmanuel Florac
2010-09-17 19:57 ` Peter Grandi
2010-09-18 11:39 ` Emmanuel Florac
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=20100819120512.GB9358@infradead.org \
--to=hch@infradead.org \
--cc=michael.monnerie@is.it-management.at \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.