public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: stan@hardwarefreak.com
Cc: xfs@oss.sgi.com
Subject: Re: howto keep xfs directory searches fast for a long time
Date: Wed, 15 Aug 2012 10:59:33 +0200	[thread overview]
Message-ID: <2157104.ZTCJzWD7Ip@saturn> (raw)
In-Reply-To: <502A83F2.6070805@hardwarefreak.com>


[-- Attachment #1.1: Type: text/plain, Size: 1390 bytes --]

Am Dienstag, 14. August 2012, 11:59:30 schrieb Stan Hoeppner:
> All the media players have playlist and index features.  So there's
> little need for searching an entire Samba share is there?

Media Players usually connect to a Samba/NFS share, and read contents. 
Some even search for index JPGs, and present that for a sub-dir so you 
have a preview. All that is directory access.

> What you apparently require is not something that can be addressed or
> optimized by filesystem or kernel tweaks.  As Dave pointed out with
> the 'locate' example in a CLI, this kind of thing is precisely what
> databases were designed for.

Yes, I use locate on that server of course, when I have shell access 
that's just fine. The "best effort" I can do now is to run the find 
service for locate daily morning, so inodes get pre-cached, and tune 
vm.vfs_cache_pressure = 10 to keep them in the cache. This works rather 
good. I just tried a "du -s /bigdir" again, it runs within a very short 
time (<4s) even 4h after the locate run, this is good enough. Customer 
will be happy. On the old server this took >3m, on the same hardware. A 
speedup of at least 45x is what I call efficient tuning ;-)

-- 
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc

it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

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

      reply	other threads:[~2012-08-15  8:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-12  9:14 howto keep xfs directory searches fast for a long time Michael Monnerie
2012-08-12 19:05 ` Peter Grandi
2012-08-12 19:35 ` Stan Hoeppner
2012-08-13 16:44   ` Michael Monnerie
2012-08-13 21:20     ` Stan Hoeppner
2012-08-13 23:56     ` Dave Chinner
2012-08-14  9:16       ` Michael Monnerie
2012-08-14 16:59         ` Stan Hoeppner
2012-08-15  8:59           ` Michael Monnerie [this message]

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=2157104.ZTCJzWD7Ip@saturn \
    --to=michael.monnerie@is.it-management.at \
    --cc=stan@hardwarefreak.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