All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mnelson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org"
	<ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org>
Cc: ceph-devel <ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Erasure Coding CPU Overhead Data
Date: Sat, 21 Feb 2015 12:22:56 -0600	[thread overview]
Message-ID: <54E8CD00.5050606@redhat.com> (raw)

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

Hi All,

Last spring at the tail end of Firefly development we ran tests looking 
at erasure coding performance both during simple RADOS read/write tests 
and also during an OSD recovery event.  Recently we were asked if we had 
any data on CPU usage overhead with erasure coding.  We had collected 
CPU utilization statistics when we ran our tests, so we went back and 
plotted the CPU utilization results and wrote up a short document based 
on those plots.  This data is fairly old at this point so it's probably 
not going to be relevant for Hammer and may not be relevant for more 
recent releases of Firefly.

This system had 30 OSDs configured and 12 2.0GHz XEON cores which is 
likely slightly underpowered for EC.  Interestingly CPU usage for small 
object writes was not significantly higher than with replication though 
overall performance was quite a bit lower.  Let me know if you have any 
questions!

Thanks,
Mark

[-- Attachment #2: Ceph_Firefly_EC_CPU_Usage.pdf --]
[-- Type: application/pdf, Size: 244469 bytes --]

[-- Attachment #3: Type: text/plain, Size: 178 bytes --]

_______________________________________________
ceph-users mailing list
ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

             reply	other threads:[~2015-02-21 18:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-21 18:22 Mark Nelson [this message]
     [not found] ` <54E8CD00.5050606-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-02-23 19:41   ` Erasure Coding CPU Overhead Data Nick Fisk
     [not found]     ` <DB3PR06MB187C4908492F8EFC0578AA5E7290-5Qr72V/tsOA6G1BGxDT3KL9PrO6axcR4XA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
2015-02-23 20:15       ` 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=54E8CD00.5050606@redhat.com \
    --to=mnelson-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ceph-users-idqoXFIVOFJgJs9I8MT0rw@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 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.