From: Avi Miller <avi.miller@oracle.com>
To: Casper Bnag <casper.bang@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Experiences: Why BTRFS had to yield for ZFS
Date: Mon, 17 Sep 2012 20:58:16 +1000 [thread overview]
Message-ID: <DB9AC79F-4AD3-48EE-9C08-E1015DBE8BBD@oracle.com> (raw)
In-Reply-To: <loom.20120917T123219-86@post.gmane.org>
Hi,
On 17/09/2012, at 8:47 PM, Casper Bnag <casper.bang@gmail.com> wrote:
> month, that just makes me wonder why Oracle didn't use these latest bits.
We used the most stable release of btrfs that was available when the development of the UEK was done. Keep in mind that while it's versioned at 2.6.39, it's actually 3.0.16 under the hood. It's just that some userspace doesn't like having a kernel version that doesn't start with "2.6"
>> 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.
Perhaps, but ASM would provide all the functionality you require, including snapshots and rollback, at the highest possible performance. Certainly a lot higher than both ZFS and btrfs. And it's fully certified and supported by Oracle.
As an alternative, why not consider using Oracle VM on the machine and creating database VMs instead? You can then use the snapshot capability of Oracle VM while still running supported and certified filesystems inside each guest.
(We should also probably take this discussion off-list, as it has drifted away from btrfs proper). Feel free to reply to me directly if you want.
--
Oracle <http://www.oracle.com>
Avi Miller | Principal Program Manager | +61 (412) 229 687
Oracle Linux and Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia
next prev parent reply other threads:[~2012-09-17 10:58 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
2012-09-17 10:58 ` Avi Miller [this message]
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=DB9AC79F-4AD3-48EE-9C08-E1015DBE8BBD@oracle.com \
--to=avi.miller@oracle.com \
--cc=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).