All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mnelson@redhat.com>
To: Andrei Mikhailovsky <andrei@arhont.com>
Cc: ceph-users@lists.ceph.com, ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: [ceph-users] Ceph Dumpling/Firefly/Hammer SSD/Memstore performance comparison
Date: Wed, 18 Feb 2015 09:44:57 -0600	[thread overview]
Message-ID: <54E4B379.3000205@redhat.com> (raw)
In-Reply-To: <413428.1082.1424272098009.JavaMail.andrei@tuchka>

Hi Andrei,

On 02/18/2015 09:08 AM, Andrei Mikhailovsky wrote:
>
> Mark, many thanks for your effort and ceph performance tests. This puts
> things in perspective.
>
> Looking at the results, I was a bit concerned that the IOPs performance
> in niether releases come even marginally close to the capabilities of
> the underlying ssd device. Even the fastest PCI ssds have only managed
> to achieve about the 1/6th IOPs of the raw device.

Perspective is definitely good!  Any time you are dealing with latency 
sensitive workloads, there are a lot of bottlenecks that can limit your 
performance.  There's a world of difference between streaming data to a 
raw SSD as fast as possible and writing data out to a distributed 
storage system that is calculating data placement, invoking the TCP 
stack, doing CRC checks, journaling writes, invoking the VM layer to 
cache data in case it's hot (which in this case it's not).

>
> I guess there is a great deal more optimisations to be done in the
> upcoming LTS releases to make the IOPs rate close to the raw device
> performance.

There is definitely still room for improvement!  It's important to 
remember though that there is always going to be a trade off between 
flexibility, data integrity, and performance.  If low latency is your 
number one need before anything else, you are probably best off 
eliminating as much software as possible between you and the device 
(except possibly if you can make clever use of caching).  While Ceph 
itself is some times the bottleneck, in many cases we've found that 
bottlenecks in the software that surrounds Ceph are just as big 
obstacles (filesystem, VM layer, TCP stack, leveldb, etc).  If you need 
a distributed storage system that can universally maintain native SSD 
levels of performance, the entire stack has to be highly tuned.

>
> I have done some testing in the past and noticed that despite the server
> having a lot of unused resources (about 40-50% server idle and about
> 60-70% ssd idle) the ceph would not perform well when used with ssds. I
> was testing with Firefly + auth and my IOPs rate was around the 3K mark.
> Something is holding ceph back from performing well with ssds (((

Out of curiosity, did you try the same tests directly on the SSD?

>
> Andrei
>
> ------------------------------------------------------------------------
>
>     *From: *"Mark Nelson" <mnelson@redhat.com>
>     *To: *"ceph-devel" <ceph-devel@vger.kernel.org>
>     *Cc: *ceph-users@lists.ceph.com
>     *Sent: *Tuesday, 17 February, 2015 5:37:01 PM
>     *Subject: *[ceph-users] Ceph Dumpling/Firefly/Hammer SSD/Memstore
>     performance        comparison
>
>     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.
>
>     Mark
>
>     _______________________________________________
>     ceph-users mailing list
>     ceph-users@lists.ceph.com
>     http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>
>

  reply	other threads:[~2015-02-18 15:45 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     ` Mark Nelson [this message]
2015-02-23  5:09 ` [ceph-users] " Gregory Farnum
2015-02-23  5:34   ` Haomai Wang
2015-02-23 14:46   ` Mark Nelson

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=54E4B379.3000205@redhat.com \
    --to=mnelson@redhat.com \
    --cc=andrei@arhont.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ceph-users@lists.ceph.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.