From: Alexandre DERUMIER <aderumier-U/x3PoR4x10AvxtiuMwx3w@public.gmane.org>
To: Mark Nelson <mnelson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: ceph-devel <ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
ceph-users <ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org>
Subject: Re: Ceph Dumpling/Firefly/Hammer SSD/Memstore performance comparison
Date: Wed, 18 Feb 2015 17:57:10 +0100 (CET) [thread overview]
Message-ID: <969587995.1268132.1424278630509.JavaMail.zimbra@oxygem.tv> (raw)
In-Reply-To: <1106171324.1261740.1424278497950.JavaMail.zimbra-M8QNeUgB6UTyG1zEObXtfA@public.gmane.org>
>>I don't have really good insight yet into how tweaking these would
>>affect single-osd performance. I know the PCIe SSDs do have multiple
>>controllers on-board so perhaps increasing the number of shards would
>>improve things, but I suspect that going too high could maybe start
>>hurting performance as well. Have you done any testing here? It could
>>be an interesting follow-up paper.
I think it should be tunned regarding number of osds and number of cores you have.
I have done test in past with sommath values
osd_op_num_threads_per_shard = 1
osd_op_num_shards = 25
filestore_fd_cache_size = 64
filestore_fd_cache_shards = 32
But don't have take time to try differents values.
But I was to be able to reach 120000iops 4k read with 3osd if I remember. (But I was limited by client cpu)
I'm going to do big benchmark next month (3 nodes (20cores) with 6ssd each),
So I'll try to test different sharding values, with different number of osd.
----- Mail original -----
De: "Mark Nelson" <mnelson@redhat.com>
À: "aderumier" <aderumier@odiso.com>
Cc: "ceph-devel" <ceph-devel@vger.kernel.org>, "ceph-users" <ceph-users@lists.ceph.com>
Envoyé: Mercredi 18 Février 2015 15:56:44
Objet: Re: [ceph-users] Ceph Dumpling/Firefly/Hammer SSD/Memstore performance comparison
Hi Alex,
Thanks! I didn't tweak the sharding settings at all, so they are just
at the default values:
OPTION(osd_op_num_threads_per_shard, OPT_INT, 2)
OPTION(osd_op_num_shards, OPT_INT, 5)
I don't have really good insight yet into how tweaking these would
affect single-osd performance. I know the PCIe SSDs do have multiple
controllers on-board so perhaps increasing the number of shards would
improve things, but I suspect that going too high could maybe start
hurting performance as well. Have you done any testing here? It could
be an interesting follow-up paper.
Mark
On 02/18/2015 02:34 AM, Alexandre DERUMIER wrote:
> Nice Work Mark !
>
> I don't see any tuning about sharding in the config file sample
>
> (osd_op_num_threads_per_shard,osd_op_num_shards,...)
>
> as you only use 1 ssd for the bench, I think it should improve results for hammer ?
>
>
>
> ----- Mail original -----
> De: "Mark Nelson" <mnelson@redhat.com>
> À: "ceph-devel" <ceph-devel@vger.kernel.org>
> Cc: "ceph-users" <ceph-users@lists.ceph.com>
> Envoyé: Mardi 17 Février 2015 18:37:01
> Objet: [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
> --
> 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
>
_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
next prev parent reply other threads:[~2015-02-18 16:57 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
[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-17 20:16 ` 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 [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=969587995.1268132.1424278630509.JavaMail.zimbra@oxygem.tv \
--to=aderumier-u/x3por4x10avxtiumwx3w@public.gmane.org \
--cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org \
--cc=mnelson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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