public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: Nathan Scott <nscott@aconex.com>,
	"Jeffrey W. Baker" <jwbaker@acm.org>,
	zfs-discuss@opensolaris.org, xfs@oss.sgi.com,
	linux-ext4@vger.kernel.org
Subject: Re: ZFS, XFS, and EXT4 compared
Date: Thu, 30 Aug 2007 13:57:28 -0500	[thread overview]
Message-ID: <46D71318.2050604@sandeen.net> (raw)
In-Reply-To: <20070830132002.GA4086@infradead.org>

Christoph Hellwig wrote:
> On Thu, Aug 30, 2007 at 05:07:46PM +1000, Nathan Scott wrote:
>> To improve metadata performance, you have many options with XFS (which
>> ones are useful depends on the type of metadata workload) - you can try
>> a v2 format log, and mount with "-o logbsize=256k", try increasing the
>> directory block size (e.g. mkfs.xfs -nsize=16k, etc), and also the log
>> size (mkfs.xfs -lsize=XXXXXXb).
> 
> Okay, these suggestions are one too often now.  v2 log and large logs/log
> buffers are the almost universal suggestions, and we really need to make
> these defaults.  XFS is already the laughing stock of the Linux community
> due to it's absurdely bad default settings.

Agreed on reevaluating the defaults, Christoph!

barrier seems to hurt badly on xfs, too.  Note: barrier is off by
default on ext[34], so if you want apples to apples there, you need to
change one or the other filesystem's mount options.  If your write cache
is safe (battery backed?) you may as well turn barriers off.  I'm not
sure offhand who will react more poorly to an evaporating write cache
(with no barriers), ext4 or xfs...

-Eric

  reply	other threads:[~2007-08-30 18:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30  6:16 ZFS, XFS, and EXT4 compared Jeffrey W. Baker
2007-08-30  6:25 ` [zfs-discuss] " Cyril Plisko
2007-08-30  6:27 ` mike
2007-08-30  7:07 ` Nathan Scott
2007-08-30 13:20   ` Christoph Hellwig
2007-08-30 18:57     ` Eric Sandeen [this message]
2007-08-30 19:09       ` Jeffrey W. Baker
2007-08-30 19:14         ` Eric Sandeen
2007-08-30 22:42     ` Nathan Scott
2007-09-01 15:07       ` Federico Sevilla III
2007-09-02 23:00         ` Nathan Scott
2007-08-30 13:37 ` Jose R. Santos
2007-08-30 18:52   ` Jeffrey W. Baker
2007-08-30 19:53     ` Jose R. Santos
2007-08-30 18:33 ` [zfs-discuss] " Jim Mauro
2007-08-30 19:07 ` eric kustarz

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=46D71318.2050604@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=hch@infradead.org \
    --cc=jwbaker@acm.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=nscott@aconex.com \
    --cc=xfs@oss.sgi.com \
    --cc=zfs-discuss@opensolaris.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