linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gionatan Danti <g.danti@assyoma.it>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Slow file stat/deletion
Date: Fri, 28 Apr 2017 22:14:54 +0200	[thread overview]
Message-ID: <a3e391cf2ce08858aef806d5f052f73e@assyoma.it> (raw)
In-Reply-To: <a37b6669-4ec1-074e-de51-ae15aee5a7d9@assyoma.it>

Hi all,
this is a note which can be useful to someone searching for the same 
thing: using "ftype=1" at mkfs time (which is, by the way, the default 
for CRC-enabled filesystem) greatly speed-up stat/find operations.

On a test case with 1.000.000 files and 1000 total directories, "find 
/mnt/xfs" time has fallen from ~70 to ~20 seconds.

As a side question: there is no method/possibility to enable ftype=1 to 
an already existing filesystem, right?
Thanks.

Il 29-11-2016 08:53 Gionatan Danti ha scritto:
> On 28/11/2016 22:53, Dave Chinner wrote:
>> 
>> Nope. There's always going to be a penalty for subverting the
>> filesystem's physical layout optimisations on storage subsystems
>> that require physical layout optimisation for performance.
>> 
>> Cheers,
>> 
>> Dave.
>> 
> 
> Ok, very clear.
> 
> Thank you for taking the time to explain, Dave.

-- 
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8

  reply	other threads:[~2017-04-28 20:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-25 10:40 Slow file stat/deletion Gionatan Danti
2016-11-27 22:14 ` Dave Chinner
2016-11-28  9:51   ` Gionatan Danti
2016-11-28 21:53     ` Dave Chinner
2016-11-29  7:53       ` Gionatan Danti
2017-04-28 20:14         ` Gionatan Danti [this message]
2017-04-28 21:03           ` Eric Sandeen

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=a3e391cf2ce08858aef806d5f052f73e@assyoma.it \
    --to=g.danti@assyoma.it \
    --cc=david@fromorbit.com \
    --cc=linux-xfs@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).