From: Eric Sandeen <sandeen@sandeen.net>
To: Jeff Flowers <ragepie@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS Best Practices
Date: Thu, 20 Aug 2009 10:23:25 -0500 [thread overview]
Message-ID: <4A8D6A6D.405@sandeen.net> (raw)
In-Reply-To: <a0531a500908200800m3f5ea065v818c97e845042221@mail.gmail.com>
Jeff Flowers wrote:
> I am going to use XFS on a Arch Linux box and I am looking for ways to
> maximize XFS performance. According to an article I have read [1],
> best XFS performance was reached with a file system formatted with a
> 64MB log and mounted with 8 log buffers and atime disabled. But I am
> curious, from the prespective of the XFS experts of this list, if this
> is still good advice and if it is still relevant, as this article was
> published in 2003.
Based on the information you've provided about the performance issues
you're seeing with your particular workload (i.e., nothing), the
existing defaults are perfect for you. :)
> Also, I have seen a few people recommend turning off the internal
> buffers of hard drives (via hdparm) when using a file system like XFS.
> Good advice?
When drive write caches lose power it may lead to inconsistencies in a
journaling filesystem like xfs, which relies on data hitting the disk in
a certain order, more or less. By default xfs issues barriers to
enforce this ordering; this has the effect of flushing the write cache
to make it safe. In some cases disabling barriers and also disabling
write cache may be a good choice.
If you "never" lose power (good ups?) then write caching is safe even
w/o barriers.
-Eric
> Thank you!
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-08-20 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 15:00 XFS Best Practices Jeff Flowers
2009-08-20 15:23 ` Eric Sandeen [this message]
2009-08-20 15:45 ` Jeff Flowers
2009-08-20 15:58 ` Eric Sandeen
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=4A8D6A6D.405@sandeen.net \
--to=sandeen@sandeen.net \
--cc=ragepie@gmail.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