CEPH filesystem development
 help / color / mirror / Atom feed
From: Stefan Priebe <s.priebe@profihost.ag>
To: ceph-devel@vger.kernel.org
Subject: 10 times higher disk load with btrfs
Date: Mon, 05 Jan 2015 19:36:37 +0100	[thread overview]
Message-ID: <54AAD9B5.5080207@profihost.ag> (raw)

Hi devs,

while btrfs is now declared as stable ;-) i wanted to retest btrfs on 
our production cluster on 2 out of 54 osds. So if they crash it doesn't 
hurt.

While if those OSDs run XFS have spikes of 20MB/s every 4-7s. The same 
OSDs after formatting them with btrfs have spikes of 190MB/s every 4-7s.

Why does just another filesystem raises the disk load by a factor of 10?

I'm running dumpling.

Greets Stefan

             reply	other threads:[~2015-01-05 18:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 18:36 Stefan Priebe [this message]
2015-01-05 19:19 ` 10 times higher disk load with btrfs Stefan Priebe
2015-01-05 19:25   ` Sage Weil
2015-01-05 20:20     ` Stefan Priebe
2015-01-05 20:29       ` Mark Nelson
2015-01-05 20:33         ` Stefan Priebe
     [not found]           ` <713980925.3244877.1420515858378.JavaMail.zimbra@oxygem.tv>
2015-01-06  3:44             ` Alexandre DERUMIER
2015-01-06  7:01               ` Stefan Priebe - Profihost AG

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=54AAD9B5.5080207@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=ceph-devel@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