From: Richard Scobie <richard@sauce.co.nz>
To: xfs@oss.sgi.com
Cc: b.candler@pobox.com
Subject: Re: Fragmentation Issue We Are Having
Date: Fri, 20 Apr 2012 07:54:50 +1200 [thread overview]
Message-ID: <4F906D8A.9040504@sauce.co.nz> (raw)
Brian Candler wrote:
--------------------------
Ah, that's new to me. So with inode32 and
sysctl fs.xfs.rotorstep=255
you can get roughly the same locality benefit for sequentially-written files
as inode64? (Aside: if you have two processes writing files to two
different
directories, will they end up mixing their files in the same AG? That
could hurt performance at readback time if reading them sequentially)
-----------------------------
The "filestreams" mount option may be of use here, see:
http://xfs.org/docs/xfsdocs-xml-dev/XFS_User_Guide//tmp/en-US/html/ch06s16.html
and page 17 of:
http://oss.sgi.com/projects/xfs/training/xfs_slides_06_allocators.pdf
Regards,
Richard
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-04-19 19:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 19:54 Richard Scobie [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-12 1:04 Fragmentation Issue We Are Having David Fuller
2012-04-12 2:16 ` Dave Chinner
2012-04-12 2:55 ` David Fuller
2012-04-12 4:24 ` Eric Sandeen
2012-04-12 7:57 ` Brian Candler
2012-04-13 0:09 ` David Fuller
2012-04-13 7:19 ` Brian Candler
2012-04-13 7:56 ` Dave Chinner
2012-04-13 8:17 ` Brian Candler
2012-04-17 0:26 ` Dave Chinner
2012-04-17 8:58 ` Brian Candler
2012-04-18 1:36 ` Dave Chinner
2012-04-18 9:00 ` Brian Candler
2012-04-19 23:12 ` Dave Chinner
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=4F906D8A.9040504@sauce.co.nz \
--to=richard@sauce.co.nz \
--cc=b.candler@pobox.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