All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mnelson@redhat.com>
To: ceph-devel <ceph-devel@vger.kernel.org>, cbt@lists.ceph.com
Subject: Ceph Community Lab: Understanding where the QA suites spend time
Date: Wed, 19 Aug 2015 14:46:44 -0500	[thread overview]
Message-ID: <55D4DD24.9010100@redhat.com> (raw)

Hi Guys,

About a month ago we were going through the process of trying to figure 
out how to replace some of the hardware in the community laboratory that 
runs all of the nightly Teuthology tests.  Given a limited budget to 
replace the existing nodes, we wanted to understand how the current QA 
suites actually spend time on the hardware.  To do this, we investigated 
the composition of suites, the amount of time that is spent in each 
suite, and then a deeper dive into how the most resource intensive jobs 
spend their time.  We then wrote a new benchmark for CBT to run 
ceph-test-rados in a rather naive reproduction of what the ceph task in 
teuthology does and tested it against several different storage device 
configurations to see how much benefit SSDs in the nodes may provide.

A couple of folks at the Hackathon were interested in the paper we 
wrote.  I thought I would share it with the community as well in case 
any folks ever wondered what Teuthology actually spends it's time doing.

http://nhm.ceph.com/community/Ceph_Community_Lab_Performance_Investigation.pdf

Thanks,
Mark

             reply	other threads:[~2015-08-19 19:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19 19:46 Mark Nelson [this message]
2015-08-19 22:05 ` [Cbt] Ceph Community Lab: Understanding where the QA suites spend time Loic Dachary
2015-08-19 22:08   ` Mark Nelson
2015-08-19 22:22     ` Loic Dachary
2015-08-19 22:36       ` Shinobu Kinjo

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=55D4DD24.9010100@redhat.com \
    --to=mnelson@redhat.com \
    --cc=cbt@lists.ceph.com \
    --cc=ceph-devel@vger.kernel.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 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.