From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs-oss <xfs@oss.sgi.com>
Subject: howto keep xfs directory searches fast for a long time
Date: Sun, 12 Aug 2012 11:14:22 +0200 [thread overview]
Message-ID: <6344220.LKveJofnHA@saturn> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1653 bytes --]
I need a VMware VM that has 8TB storage. As I can at max create a 2TB
disk, I need to add 4 disks, and use lvm to concat these. All is on top
of a RAID5 or RAID6 store.
The workload will be storage of mostly large media files (5TB mkv Video
+ 1TB mp3), plus backup of normal documents (1TB .odt,.doc,.pdf etc).
The server should be able to find files quickly, transfer speed is not
important. There won't be many deletes to media files, mostly uploads
and searching for files. Only when it grows full, old files will be
removed. But normal documents will be rsynced (used as backup
destination) regularly.
I will set vm.vfs_cache_pressure = 10, this helps at least keeping
inodes cached when they were read once.
- What is the best setup to get high speed on directory searches? Find,
ls, du, etc. should be quick.
- Should I use inode64 or not?
- If that's an 8 disk RAID-6, should I mkfs.xfs with 6*4 AGs? Or what
would be a good start, or wouldn't it matter at all?
And as it'll be mostly big media files, should I use sunit/swidth set to
64KB/6*64KB, does that make sense?
I'm asking because I had such a VM setup once, and while it was fairly
quick in the beginning, over time it felt much slower on traversing
directories, very seek bound. That xfs was only 80% filled, so shouldn't
have had a fragmentation problem. And I know nothing to fix that apart
from backup/restore, so maybe there's something to prevent that?
--
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
next reply other threads:[~2012-08-12 9:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-12 9:14 Michael Monnerie [this message]
2012-08-12 19:05 ` howto keep xfs directory searches fast for a long time 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
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=6344220.LKveJofnHA@saturn \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox