public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Ems <richard.ems@cape-horn-eng.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: XFS unlink still slow on 3.1.9 kernel ?
Date: Mon, 13 Feb 2012 18:53:20 +0100	[thread overview]
Message-ID: <4F394E10.9000804@cape-horn-eng.com> (raw)
In-Reply-To: <20120213172937.GA25248@infradead.org>

On 02/13/2012 06:29 PM, Christoph Hellwig wrote:
> On Mon, Feb 13, 2012 at 06:26:46PM +0100, Richard Ems wrote:
>> YES. All files (and dirs) that I checked do show something as
>>
>> 0: [0..7]: 18531216..18531223
>>
>> So, what improvements can I expect from a kernel > 3.2 ?
>> Can I read somewhere about the changes/patches introduced?
> 
> On some crazy workloads I've seen speedups up to a factor of 10.000 (5
> orders or magnitude).  You probably won't get that much of a speedup,
> but it will still be significant.
> 
> The patch in mainline for this is:
> 
> commit 859f57ca00805e6c482eef1a7ab073097d02c8ca
> Author: Christoph Hellwig <hch@infradead.org>
> Date:   Sat Aug 27 14:45:11 2011 +0000
> 
>     xfs: avoid synchronous transactions when deleting attr blocks
> 
>> Is there another way to mount/create/mkfs the XFS to improve the unlink
>> time for this case?
> 
> Try increasing the inode size during filesystem creating using the
> "-i size=512" option or even "-i size=1024" if you still have
> out of line attributes.  The should give you even bigger speedups
> for this workload than the patch above.
> 

Ok, Many thanks for this good info!

I will try to install a > 3.2 kernel and will create new XFS partitions
with "-i size=1024", since we use ACLs a lot for user access.
Is there a chance to change existing XFS partitions to "-i size=1024" ?
I already have 5 big partitions, all full of ACLs and not running
kernels > 3.2 !

Many thanks again,
Richard


-- 
Richard Ems       mail: Richard.Ems@Cape-Horn-Eng.com

Cape Horn Engineering S.L.
C/ Dr. J.J. Dómine 1, 5º piso
46011 Valencia
Tel : +34 96 3242923 / Fax 924
http://www.cape-horn-eng.com

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

  reply	other threads:[~2012-02-13 17:53 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13 16:57 XFS unlink still slow on 3.1.9 kernel ? Richard Ems
2012-02-13 17:08 ` Christoph Hellwig
2012-02-13 17:11   ` Richard Ems
2012-02-13 17:15     ` Christoph Hellwig
2012-02-13 17:26       ` Richard Ems
2012-02-13 17:29         ` Christoph Hellwig
2012-02-13 17:53           ` Richard Ems [this message]
2012-02-13 18:02             ` Christoph Hellwig
2012-02-13 18:06               ` Richard Ems
2012-02-13 18:10                 ` Christoph Hellwig
2012-02-13 18:18                   ` Richard Ems
2012-02-13 18:48                   ` Richard Ems
2012-02-13 21:16                     ` Christoph Hellwig
2012-02-14  5:31                       ` Stan Hoeppner
2012-02-14  9:48                       ` Richard Ems
2012-02-14 19:43                         ` Christoph Hellwig
2012-02-14  9:49                       ` Richard Ems
2012-02-14 10:54                       ` Richard Ems
2012-02-14 11:44                       ` Richard Ems
2012-02-14  0:09 ` Dave Chinner
2012-02-14 12:32   ` Richard Ems
2012-02-14 19:45     ` Christoph Hellwig
2012-02-15 12:07       ` Richard Ems
2012-02-15  1:27     ` Dave Chinner
2012-02-15 12:07       ` Richard Ems
  -- strict thread matches above, loose matches on Subject: below --
2012-02-14 13:02 Richard Ems
     [not found] ` <4F3AA191.9030606@mnsu.edu>
2012-02-14 18:12   ` Richard Ems
2012-02-14 19:07     ` Christoph Hellwig
2012-02-15 12:48       ` Richard Ems
2012-02-14 23:10 ` Stan Hoeppner
2012-02-15 15:54   ` Richard Ems

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=4F394E10.9000804@cape-horn-eng.com \
    --to=richard.ems@cape-horn-eng.com \
    --cc=hch@infradead.org \
    --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