public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nscott@aconex.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Jeffrey W. Baker" <jwbaker@acm.org>,
	xfs@oss.sgi.com, linux-ext4@vger.kernel.org
Subject: Re: ZFS, XFS, and EXT4 compared
Date: Fri, 31 Aug 2007 08:42:31 +1000	[thread overview]
Message-ID: <1188513751.24970.109.camel@edge.yarra.acx> (raw)
In-Reply-To: <20070830132002.GA4086@infradead.org>

[culled zfs-discuss from CC, since its subscriber-only]

On Thu, 2007-08-30 at 14:20 +0100, 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.

Possibly.  Far more importantly for XFS, there really needs to be some
way for RAID drivers to say "even though I support write barriers, its
not a good idea for filesystems to enable write barriers by default on
me".  Enabling write barriers everywhere, by default, seems to have a
far worse impact than any mkfs/mount option tweaking.

>   XFS is already the laughing stock of the Linux community
> due to it's absurdely bad default settings.

Oh, _thats_ what everyone's laughing at?

cheers.

--
Nathan

  parent reply	other threads:[~2007-08-30 22:41 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
2007-08-30 19:09       ` Jeffrey W. Baker
2007-08-30 19:14         ` Eric Sandeen
2007-08-30 22:42     ` Nathan Scott [this message]
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=1188513751.24970.109.camel@edge.yarra.acx \
    --to=nscott@aconex.com \
    --cc=hch@infradead.org \
    --cc=jwbaker@acm.org \
    --cc=linux-ext4@vger.kernel.org \
    --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