From: Casper Bnag <casper.bang@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Experiences: Why BTRFS had to yield for ZFS
Date: Mon, 17 Sep 2012 10:47:44 +0000 (UTC) [thread overview]
Message-ID: <loom.20120917T123219-86@post.gmane.org> (raw)
In-Reply-To: 55422103-3EA7-4DE9-9C47-351CBD006871@oracle.com
> Oracle Database is not certified to run on either btrfs or ZFS on Linux, so if
certification is an issue, you can't use either filesystem.
Right, I had missed that - only ZFS on Solaris is officially supported I
suppose. We had to draw the line somewhere, and an Oracle OS with an Oracle
database with an Oracle filesystem seemed like a good platform. If the BTRFS
pieces are indeed a year old in the latest official binary kernel from last
month, that just makes me wonder why Oracle didn't use these latest bits.
Again, I'm inclined to think we're dealing with a design difference between
ZFS and BTRFS rather than a missing performance optimization. You'd know that
better than I. :)
> Out of interest, have you done a performance benchmark with ASM using ASMlib
> on the same platform?
Sorry, no. Our experience with ASM is limited, we came to the conclusion once
that we like being able to handle the files in a plain mountable file-system.
next prev parent reply other threads:[~2012-09-17 10:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 8:45 Experiences: Why BTRFS had to yield for ZFS Casper Bang
2012-09-17 9:15 ` Ralf Hildebrandt
2012-09-17 9:55 ` Casper Bnag
2012-09-17 10:05 ` Avi Miller
2012-09-17 10:47 ` Casper Bnag [this message]
2012-09-17 10:58 ` Avi Miller
2012-09-18 16:48 ` Andrew McGlashan
2012-09-18 21:46 ` Avi Miller
2012-09-18 5:28 ` Anand Jain
2012-09-19 7:28 ` Casper Bang
2012-09-19 7:36 ` Fajar A. Nugraha
2012-09-19 8:09 ` Casper Bang
2012-09-18 23:08 ` Gregory Farnum
2012-09-19 15:25 ` Chris Mason
2012-09-19 19:43 ` Casper Bang
2012-10-08 14:38 ` Casper Bang
2012-10-08 20:59 ` Avi Miller
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=loom.20120917T123219-86@post.gmane.org \
--to=casper.bang@gmail.com \
--cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).