From: "Tom" <T-o-m@gmx.net>
To: xfs@oss.sgi.com
Subject: Which XFS-options for best performance in my case?
Date: Thu, 2 Oct 2008 17:10:33 +0300 [thread overview]
Message-ID: <001d01c92498$a4bd7b40$ee3871c0$@net> (raw)
Hello dear list members,
I am setting up a fileserver with the following specs:
. Hardware RAID 6 (3Ware 9650SE-12, 8-lane-PCIe) with a stripe size
of 64kB, write cache enabled
. 12 Harddisks, 1 Terrabyte and 32MB cache each, 7200 RPM
. Motherboard: ASUS P5BV-E/4L
. CPU: Intel Core2Quad 2,4 GHz (Q6600)
. RAM: 2x2 GB DDRII ECC 800MHz
. OS: Linux openSUSE 11 - 64 Bit
. Kernel: 2.6.25.16-0.1-default
. Filesystem of relevant data partition: XFS
. Size of relevant data partition: 9 Terrabyte
. The data hosted on this partition is going to be served via 4
1-Gigabit-Network-cards to Windows Vista-64-SP1 clients via Samba 3.2.3-0.1
After having fine tuned the RAID-controller and the kernel settings, I am
reaching the following results: Read 465 MB/s; Write 296 MB/s, which I
benchmarked with "sync; bonnie++ -u 0 -r 4096 -b -d
/name_of_the_mounted_partition". These figures are not all to good.
I had formatted the partition with the openSUSE installation tool ("YAST").
This uses:
- Block size in bytes: auto
- Inode size: auto
- Percentage of inode space: auto
- Inode aligned: auto
.. and mounts the partition in the fstab with "defaults, 1, 2"
Question:
Are there any settings/options/tweaks with which I can increase the
XFS-filesystem's performance?
The server is connected to a UPS-battery (Uninterruptible power supply). The
RAID controller has a own battery pack attached, which keeps any cached
writings in the controller's memory, should the system hang or the power be
disconnected for any reason (but this battery only lasts for a couple of
hours).
Above everything else stands SECURITY. I can't afford to lose/corrupt any
data on this server. So please tell me if one of the proposed tweaks should
be risky, or what the risks are.
Thank you for any piece of advice/information!
Best regards
Tom
[[HTML alternate version deleted]]
next reply other threads:[~2008-10-02 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 14:10 Tom [this message]
2008-10-02 15:54 ` Which XFS-options for best performance in my case? Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2008-10-02 14:28 Tom
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='001d01c92498$a4bd7b40$ee3871c0$@net' \
--to=t-o-m@gmx.net \
--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