From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: Dieter Kasper <d.kasper@kabelmail.de>
Cc: Dietmar Maurer <dietmar@proxmox.com>,
Alexandre DERUMIER <aderumier@odiso.com>,
Josh Durgin <josh.durgin@inktank.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
Andreas Bluemle <andreas.bluemle@itxperts.de>
Subject: Re: RBD performance - tuning hints / major slowdown effect(s)
Date: Fri, 31 Aug 2012 22:16:26 +1200 [thread overview]
Message-ID: <50408EFA.3000403@catalyst.net.nz> (raw)
In-Reply-To: <20120831094926.GA30653@oder.kd-bie.de>
Sorry Dieter,
Not trying to say "you are wrong" or anything like that - just trying to
add to the problem solving body of knowledge that from what *I* have
tried out the 'sync' issue does not look to be the bad guy here - altho
more analysis is always welcome (usual story - my findings should be
confirm-able by others doing similar tests)!
regards
Mark
On 31/08/12 21:49, Dieter Kasper wrote:
> Mark, Inktank,
>
> OK, it is very likely that 'sync_file_range' is not the major slowdown 'culprit'.
>
> But, which areas (design, current implementation, protocol, interconnect, tuning parameter, ...)
> would you rate as 'major slowdown effect(s)' ?
>
next prev parent reply other threads:[~2012-08-31 10:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 10:24 Ceph write performance George Shuklin
[not found] ` <20120720104150.GA16630@oder.kd-bie.de>
2012-07-20 10:48 ` George Shuklin
2012-07-20 11:49 ` Mark Nelson
2012-07-20 20:36 ` Ceph write performance on RAM-DISK Dieter Kasper
2012-07-20 21:28 ` Mark Nelson
2012-07-20 15:53 ` Ceph write performance Matthew Richardson
2012-07-20 16:37 ` Gregory Farnum
2012-08-28 17:48 ` RBD performance - tuning hints Dieter Kasper
2012-08-28 18:53 ` Smart Weblications GmbH - Florian Wiessner
2012-08-28 19:04 ` Dieter Kasper
2012-08-29 8:50 ` Alexandre DERUMIER
2012-08-29 17:37 ` Josh Durgin
2012-08-29 19:29 ` RBD performance - tuning hints / parameter doc Dieter Kasper
2012-08-29 22:34 ` Samuel Just
2012-08-30 15:08 ` Dieter Kasper
2012-08-30 20:39 ` Samuel Just
2012-08-30 14:56 ` RBD performance - tuning hints Dieter Kasper
2012-08-30 15:28 ` Alexandre DERUMIER
2012-08-30 15:33 ` Dieter Kasper
2012-08-30 15:46 ` Alexandre DERUMIER
2012-08-30 16:02 ` Dieter Kasper
2012-08-30 16:12 ` Alexandre DERUMIER
2012-08-30 16:16 ` Josh Durgin
2012-08-31 7:46 ` Alexandre DERUMIER
2012-08-31 8:11 ` Dietmar Maurer
2012-08-31 8:48 ` Mark Kirkwood
2012-08-31 9:49 ` RBD performance - tuning hints / major slowdown effect(s) Dieter Kasper
2012-08-31 10:16 ` Mark Kirkwood [this message]
2012-08-31 10:58 ` RBD performance - tuning hints Jerker Nyberg
2012-08-30 16:48 ` Dieter Kasper
2012-08-30 18:10 ` Gregory Farnum
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=50408EFA.3000403@catalyst.net.nz \
--to=mark.kirkwood@catalyst.net.nz \
--cc=aderumier@odiso.com \
--cc=andreas.bluemle@itxperts.de \
--cc=ceph-devel@vger.kernel.org \
--cc=d.kasper@kabelmail.de \
--cc=dietmar@proxmox.com \
--cc=josh.durgin@inktank.com \
/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.