From: Eric Sandeen <sandeen@sandeen.net>
To: "Jeffrey W. Baker" <jwbaker@acm.org>
Cc: 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 14:14:04 -0500 [thread overview]
Message-ID: <46D716FC.9030905@sandeen.net> (raw)
In-Reply-To: <1188500941.8980.20.camel@toonses.gghcwest.com>
Jeffrey W. Baker wrote:
> On Thu, 2007-08-30 at 13:57 -0500, Eric Sandeen wrote:
>> 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...
>
> I didn't compare the safety of the three filesystems,
Understood
> but I did have
> disk caches disabled
Oh, so for the SW raid tests the individual disks had no write cache?f
> and only battery-backed caches enabled. Do you
> need barriers without volatile caches?
As far as I understand it, then nope, you don't need it, and you're
hurting performance with it.
-Eric
next prev parent reply other threads:[~2007-08-30 19:13 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 [this message]
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=46D716FC.9030905@sandeen.net \
--to=sandeen@sandeen.net \
--cc=jwbaker@acm.org \
--cc=linux-ext4@vger.kernel.org \
--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