Thanks for taking the time to write this up follow through the thread.
It's always interesting to hear situations where btrfs doesn't work
well.
There are three basic problems with the database workloads on btrfs.
First is that we have higher latencies on writes because we are feeding
Hi,
On 09/10/2012, at 1:38 AM, Casper Bang casper.b...@gmail.com wrote:
If you do have a suspicion or insight on the matter (perhaps work for Oracle,
or
know OUK?), of course we'd love a followup offline this list.
I've sent an email to Casper to follow this up offline.
Thanks,
Avi
--
Anand Jain Anand.Jain at oracle.com writes:
archive-log-apply script - if you could, can you share the
script itself ? or provide more details about the script.
(It will help to understand the work-load in question).
Our setup entails a whole bunch of scripts, but the apply script looks
On Wed, Sep 19, 2012 at 2:28 PM, Casper Bang casper.b...@gmail.com wrote:
Anand Jain Anand.Jain at oracle.com writes:
archive-log-apply script - if you could, can you share the
script itself ? or provide more details about the script.
(It will help to understand the work-load in
IIRC there were some patches post-3.0 which relates to sync. If oracle
db uses sync writes (or call sync somewhere, which it should), it
might help to re-run the test with more recent kernel. kernel-ml
repository might help.
Yeah there doesn't seem to be a shortage of patches coming into
On Mon, Sep 17, 2012 at 02:45:08AM -0600, Casper Bang wrote:
Abstract
For database testing purposes, a COW filesystem was needed in order to
facilitate snapshotting and rollback, such as to provide mirrors of
our production database at fixed intervals (every night and by
demand).
Thanks for
Chris Mason chris.mason at fusionio.com writes:
There are three basic problems with the database workloads on btrfs.
First is that we have higher latencies on writes because we are feeding
everything through helper threads for crcs. Usually the extra latencies
don't show up because we have
Hi,
On 17/09/2012 8:05 PM, Avi Miller wrote:
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. Out of
interest, have you done a performance benchmark with ASM using ASMlib on the
same platform?
I
Hi,
On 19/09/2012, at 2:48 AM, Andrew McGlashan
andrew.mcglas...@affinityvision.com.au wrote:
On 17/09/2012 8:05 PM, Avi Miller wrote:
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. Out of
On Mon, Sep 17, 2012 at 1:45 AM, Casper Bang casper.b...@gmail.com wrote:
Abstract
For database testing purposes, a COW filesystem was needed in order to
facilitate snapshotting and rollback, such as to provide mirrors of
our production database at fixed intervals (every night and by
demand).
Abstract
For database testing purposes, a COW filesystem was needed in order to
facilitate snapshotting and rollback, such as to provide mirrors of
our production database at fixed intervals (every night and by
demand).
Platform
An HP Proliant 380P (2x Intel Xeon E5-2620 with 12 cores for a total
* Casper Bang casper.b...@gmail.com:
Oracle (Unbreakable) Linux x64 2.6.39-200.29.3.el6uek.x86_64 #1 SMP
And the btrfs was that from vanilla 2.6.39 (i.e. over a year old)?
--
Ralf Hildebrandt Charite Universitätsmedizin Berlin
ralf.hildebra...@charite.deCampus
Hi,
On 17/09/2012, at 7:55 PM, Casper Bnag casper.b...@gmail.com wrote:
We're using the latest available kernel for our Oracle Unbreakable
Linux 6.3 from Aug 28. We have no other option, since the Oracle database
software needs to run on a certified distro.
Oracle Database is not certified
Hi,
On 17/09/2012, at 8:47 PM, Casper Bnag casper.b...@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
A script on the test server, would then apply Oracle archive files
from the production environment to this Oracle sync database, every
10'th minute, effectively making it near up-to-date with production.
The most reliable way to do this was with a simple NFS mount (rather
than rsync or
15 matches
Mail list logo
