> 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
Chris Mason 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 enough work
> 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 b
> Anand Jain 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 like
th
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
