All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mnelson@redhat.com>
To: Gregory Farnum <greg@gregs42.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: [ceph-users] Ceph Dumpling/Firefly/Hammer SSD/Memstore performance comparison
Date: Mon, 23 Feb 2015 08:46:41 -0600	[thread overview]
Message-ID: <54EB3D51.2080308@redhat.com> (raw)
In-Reply-To: <CAC6JEv_WF9BANF_n7fPWmHFNYAKjizfV=0sHwJmKrP-uNGRfCQ@mail.gmail.com>



On 02/22/2015 11:09 PM, Gregory Farnum wrote:
> On Tue, Feb 17, 2015 at 9:37 AM, Mark Nelson <mnelson@redhat.com> wrote:
>> Hi All,
>>
>> I wrote up a short document describing some tests I ran recently to look at
>> how SSD backed OSD performance has changed across our LTS releases. This is
>> just looking at RADOS performance and not RBD or RGW.  It also doesn't offer
>> any real explanations regarding the results.  It's just a first high level
>> step toward understanding some of the behaviors folks on the mailing list
>> have reported over the last couple of releases.  I hope you find it useful.
>
> Do you have any work scheduled to examine the synchronous IO latency
> changes across versions? I suspect those are involved with the loss of
> performance some users have reported, and I've not heard any
> believable theories as to the cause. Since this is the first set of
> results pointing that way on hardware available for detailed tests I
> hope we can dig into it. And those per-op latencies are the next thing
> we'll need to cut down on, since they correspond pretty directly with
> CPU costs that we want to scale down! :)

I kind of suspect that some of the user issues might be RBD on the 
client side (or even QEMU).  Certainly possible it's OSD too though. 
With so many different kinds of hardware and so many ways to tune things 
it can be tough to narrow down.  I'm really looking forward to the work 
that's being done on LTTNG tracing.  That will give us much easier 
insight into these kinds of things than we've had in the past.

> -Greg
>

      parent reply	other threads:[~2015-02-23 14:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 17:37 Ceph Dumpling/Firefly/Hammer SSD/Memstore performance comparison Mark Nelson
2015-02-17 20:16 ` [ceph-users] " Stephen Hindle
     [not found]   ` <CANPbtN830yy7AJ6ziWr7V7sN80vHobpy7j8XwGpFizhd7fJynQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-17 20:24     ` Tyler Brekke
2015-02-17 20:25     ` Karan Singh
2015-02-17 20:28   ` [ceph-users] " Mark Nelson
2015-02-17 20:30     ` Stephen Hindle
     [not found] ` <974800637.1174441.1424248449764.JavaMail.zimbra@oxygem.tv>
2015-02-18  8:34   ` Alexandre DERUMIER
     [not found]     ` <1298645585.1174612.1424248460594.JavaMail.zimbra-M8QNeUgB6UTyG1zEObXtfA@public.gmane.org>
2015-02-18 14:56       ` Mark Nelson
     [not found]         ` <1106171324.1261740.1424278497950.JavaMail.zimbra-M8QNeUgB6UTyG1zEObXtfA@public.gmane.org>
2015-02-18 16:57           ` Alexandre DERUMIER
     [not found] ` <54E37C3D.5030702-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-02-17 18:07   ` Irek Fasikhov
2015-02-18 15:08   ` Andrei Mikhailovsky
2015-02-18 15:44     ` [ceph-users] " Mark Nelson
2015-02-23  5:09 ` Gregory Farnum
2015-02-23  5:34   ` Haomai Wang
2015-02-23 14:46   ` Mark Nelson [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=54EB3D51.2080308@redhat.com \
    --to=mnelson@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=greg@gregs42.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.