From: Mark Nelson <mnelson@redhat.com>
To: Stephen Hindle <shindle@llnw.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>,
"ceph-users@lists.ceph.com" <ceph-users@lists.ceph.com>
Subject: Re: [ceph-users] Ceph Dumpling/Firefly/Hammer SSD/Memstore performance comparison
Date: Tue, 17 Feb 2015 14:28:04 -0600 [thread overview]
Message-ID: <54E3A454.1060003@redhat.com> (raw)
In-Reply-To: <CANPbtN830yy7AJ6ziWr7V7sN80vHobpy7j8XwGpFizhd7fJynQ@mail.gmail.com>
Hi Stephen,
It's a benchmark automation tool we wrote that builds a ceph cluster and
then runs benchmarks against it. It's still pretty rough (no real error
checking, no documentation, etc). We have some partners that are
interested in using it too and I'd like to make it useful for the
community so we're going to try to make it a bit more accessible.
cbt is here:
https://github.com/ceph/ceph-tools/tree/master/cbt
We've also been using it to prototype nightly performance testing of
firefly and master for the last month or two on some of our lab nodes.
The cron job and test suites are here:
https://github.com/ceph/ceph-tools/tree/master/regression
Mark
On 02/17/2015 02:16 PM, Stephen Hindle wrote:
> I was wondering what the 'CBT' tool is ? Google is useless for that acronym...
>
> Thanks!
> Steve
>
> On Tue, Feb 17, 2015 at 10: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.
>>
>> Mark
>>
>> _______________________________________________
>> 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-17 20:28 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 ` Mark Nelson [this message]
2015-02-17 20:30 ` [ceph-users] " 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
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=54E3A454.1060003@redhat.com \
--to=mnelson@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-users@lists.ceph.com \
--cc=shindle@llnw.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.