All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Mark Nelson <mnelson@redhat.com>,
	ceph-devel <ceph-devel@vger.kernel.org>,
	cbt@lists.ceph.com
Subject: Re: [Cbt] Ceph Community Lab: Understanding where the QA suites spend time
Date: Thu, 20 Aug 2015 00:05:13 +0200	[thread overview]
Message-ID: <55D4FD99.6000508@dachary.org> (raw)
In-Reply-To: <55D4DD24.9010100@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2329 bytes --]

Hi,

To help put things in perspective (please forgive me if it's a fact already known to everyone), > 95% of the teuthology jobs can run on virtual machines with 8GB RAM, 40GB disk, 2 processors and no attached disks. The cost of running such virtual machines in the cloud currently is 0.033 euros per hour. Running 40 teuthology jobs at all times would require an average of 80 such virtual machines (most jobs use 2 machines, some 1 or 3), that is 0.033 * 80 vms * 24 hours * 31 days == ~2000 euros per month (also note that at least one cloud provider offers 50% discount if such virtual machines are reserved full time). That's 3 to 6 times cheaper than AWS. 

I'm not sure how much it costs to run these 40 teuthology jobs on a hand made lab but I'd be surprised if it was cheaper, all included. Whatever hardware already exists in the sepia lab can easily handle the remaining 5% of jobs that require actual hardware for one reason or the other.

My 3.3cts ;-)

On 19/08/2015 21:46, Mark Nelson wrote:
> 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
> _______________________________________________
> Cbt mailing list
> Cbt@lists.ceph.com
> http://lists.ceph.com/listinfo.cgi/cbt-ceph.com

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19 19:46 Ceph Community Lab: Understanding where the QA suites spend time Mark Nelson
2015-08-19 22:05 ` Loic Dachary [this message]
2015-08-19 22:08   ` [Cbt] " 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=55D4FD99.6000508@dachary.org \
    --to=loic@dachary.org \
    --cc=cbt@lists.ceph.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=mnelson@redhat.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.