From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Alexandre DERUMIER <aderumier@odiso.com>
Cc: Mark Nelson <mnelson@redhat.com>, Sage Weil <sage@newdream.net>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: 10 times higher disk load with btrfs
Date: Tue, 06 Jan 2015 08:01:02 +0100 [thread overview]
Message-ID: <54AB882E.8090809@profihost.ag> (raw)
In-Reply-To: <912779433.3244878.1420515867862.JavaMail.zimbra@oxygem.tv>
Hi,
Am 06.01.2015 um 04:44 schrieb Alexandre DERUMIER:
> Hi Stefan,
>
> Do you see a difference if you force filestore journal writeahead for btrfs instead parrallel ?
>
> filestore journal writeahead = 1
> filestore journal parallel = 0
i already tested filestore btrfs snap = false which automatically
disabled parallel write.
Stefan
> ----- Mail original -----
> De: "Stefan Priebe" <s.priebe@profihost.ag>
> À: "Mark Nelson" <mnelson@redhat.com>, "Sage Weil" <sage@newdream.net>
> Cc: "ceph-devel" <ceph-devel@vger.kernel.org>
> Envoyé: Lundi 5 Janvier 2015 21:33:22
> Objet: Re: 10 times higher disk load with btrfs
>
> Am 05.01.2015 um 21:29 schrieb Mark Nelson:
>>
>>
>> On 01/05/2015 02:20 PM, Stefan Priebe wrote:
>>> Hi Sage,
>>>
>>> Am 05.01.2015 um 20:25 schrieb Sage Weil:
>>>> On Mon, 5 Jan 2015, Stefan Priebe wrote:
>>>>>
>>>>> Am 05.01.2015 um 19:36 schrieb Stefan Priebe:
>>>>>> 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?
>>>>>
>>>>> OK this seems to happen cause ceph is creating every 5s a new
>>>>> subvolume /
>>>>> snap. Is this really expected / needed?
>>>>
>>>> You can disable it with
>>>>
>>>> filestore btrfs snap = false
>>>>
>>>> I'm curious how much this drops the load down; originally the
>>>> snaps were no more expensive than a regular sync but perhaps this
>>>> has changed...
>>>
>>> - with XFS the average write is at 9Mb/s
>>> - with btrfs (filestore_btrfs_snap=true) write is at 40Mb/s
>>> - with btrfs (filestore_btrfs_snap=false) write is at 20Mb/s
>>
>> Is that the average and not the spikes? It looks like before the spikes
>> were 20MB/s and 190MB/s?
>
> Yes these are average values.
>
> Spikes:
> - with XFS the spike write is at 20Mb/s
> - with btrfs (filestore_btrfs_snap=true) spike write is 200Mb/s
> - with btrfs (filestore_btrfs_snap=false) spike is still 185Mb/s but avg
> is 1/2 (20Mb/s) see above
>
>
>>
>>>
>>> Stefan
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-01-06 7:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 18:36 10 times higher disk load with btrfs Stefan Priebe
2015-01-05 19:19 ` 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 [this message]
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=54AB882E.8090809@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=aderumier@odiso.com \
--cc=ceph-devel@vger.kernel.org \
--cc=mnelson@redhat.com \
--cc=sage@newdream.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.