From: "R. Jason Adams" <rjasonadams@gmail.com>
To: linux-xfs@vger.kernel.org
Subject: Suggested XFS setup/options for 10TB file system w/ 18-20M files.
Date: Mon, 2 Oct 2017 09:14:07 -0400 [thread overview]
Message-ID: <65736D53-5B93-46DD-95D2-02496B59D09C@gmail.com> (raw)
Hello,
I have a use case where I'm writing ~500Kb (avg size) files to a 10TB XFS file systems. Each of system has 36 of these 10TB drives.
The application opens the file, writes the data (single call), and closes the file. In addition there are a few lines added to the extended attributes. The filesystem ends up with 18 to 20 million files when the drive is full. The files are currently spread over 128x128 directories using a hash of the filename.
The format command I'm using:
mkfs.xfs -f -i size=1024 ${DRIVE}
Mount options:
rw,noatime,attr2,inode64,allocsize=2048k,logbufs=8,logbsize=256k,noquota
As the drive is filling, the first few % of the drive seems fine. Using iostat the avgrq-sz is close to the average file size. What I'm noticing is as the drive starts to fill (say around 5-10%) the reads start increasing (r/s in iostat). In addition, the avgrq-sz starts to decrease. Pretty soon the r/s can be 1/3 to 1/2 as many as our w/s. At first we thought this was related to using extended attributes, but disabling that didn’t make a difference at all.
Considering I know the app isn’t making any read request, I’m guessing this is related to updating metadata etc. Any guidance on how to resolve/reduce/etc? For example, would a different directory structure help (more files in less directories)?
Thanks,
R. Jason Adams
next reply other threads:[~2017-10-02 13:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 13:14 R. Jason Adams [this message]
2017-10-02 13:36 ` Suggested XFS setup/options for 10TB file system w/ 18-20M files Eric Sandeen
2017-10-02 13:49 ` R. Jason Adams
2017-10-02 14:10 ` R. Jason Adams
2017-10-02 14:12 ` Eric Sandeen
2017-10-02 23:14 ` Dave Chinner
2017-10-03 18:10 ` R. Jason Adams
2017-10-03 20:32 ` 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=65736D53-5B93-46DD-95D2-02496B59D09C@gmail.com \
--to=rjasonadams@gmail.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