public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>
Cc: linux-xfs@oss.sgi.com
Subject: Re: Deleting files with extended attributes is dead slow
Date: Fri, 12 Aug 2011 16:47:46 -0400	[thread overview]
Message-ID: <20110812204746.GB30615@infradead.org> (raw)
In-Reply-To: <j23qs9$1c3$1@dough.gmane.org>

On Fri, Aug 12, 2011 at 08:19:53PM +0200, Bernd Schubert wrote:
> Hi there,
> 
> with FhGFS we may use extended attributes to store file meta data
> and with ext3/ext4 that also works very well and the rate to create
> files and to write those EAs (create() + fsetxattr()  is about 2.5
> to 3 times faster than with a create() + write(). Size of those EA
> data is about 256 bytes depending on the number of storage stripes.
> However, with XFS using extended attributes is *extremely* slow.
> Here are some numbers with ext4 and xfs using a patched [1] bonnie++

Currently XFS uses synchronous transactions when retiring inodes with
xattrs on them.  So far I've not actually found a good reason for that,
so I suspect we can remove it.  I'll do another audit of it, and will
send you a patch for it after doing basic QA.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2011-08-12 20:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12 18:19 Deleting files with extended attributes is dead slow Bernd Schubert
2011-08-12 20:47 ` Christoph Hellwig [this message]
2011-08-16 16:13   ` Christoph Hellwig
     [not found]     ` <4E4BBC98.7020501@itwm.fraunhofer.de>
2011-08-17 17:02       ` Christoph Hellwig
2011-08-17 17:39         ` Bernd Schubert
2011-08-18  2:08           ` Dave Chinner
2011-08-18  3:05             ` Dave Chinner
2011-08-22 14:35               ` Christoph Hellwig

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=20110812204746.GB30615@infradead.org \
    --to=hch@infradead.org \
    --cc=bernd.schubert@itwm.fraunhofer.de \
    --cc=linux-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