CEPH filesystem development
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: speedup ceph / scaling / find the bottleneck
Date: Fri, 29 Jun 2012 12:46:42 +0200	[thread overview]
Message-ID: <4FED8792.1090905@profihost.ag> (raw)

Hello list,

i've made some further testing and have the problem that ceph doesn't 
scale for me. I added a 4th osd server to my existing 3 node osd 
cluster. I also reformated all to be able to start with a clean system.

While doing random 4k writes from two VMs i see about 8% idle on the osd 
servers (Single Intel Xeon E5 8 cores 3,6Ghz). I believe that this is 
the limiting factor and also the reason why i don't see any improvement 
by adding osd servers.

3 nodes: 2VMS: 7000 IOp/s 4k writes osds: 7-15% idle
4 nodes: 2VMS: 7500 IOp/s 4k writes osds: 7-15% idle

Even the cpu is not the limiting factor i think it would be really 
important to lower the CPU usage while doing 4k writes. The CPU is only 
used by the ceph-osd process. I see nearly no usage by other processes 
(only 5% by kworker and 5% flush).

Could somebody recommand me a way to debug this? So we know where all 
this CPU usage goes?

Stefan

             reply	other threads:[~2012-06-29 10:46 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-29 10:46 Stefan Priebe - Profihost AG [this message]
2012-06-29 11:32 ` speedup ceph / scaling / find the bottleneck Alexandre DERUMIER
2012-06-29 11:49 ` Mark Nelson
2012-06-29 13:02   ` Stefan Priebe - Profihost AG
2012-06-29 13:11     ` Stefan Priebe - Profihost AG
2012-06-29 13:16       ` Stefan Priebe - Profihost AG
2012-06-29 13:22         ` Stefan Priebe - Profihost AG
2012-06-29 15:28     ` Sage Weil
2012-06-29 21:18       ` Stefan Priebe
2012-07-01 21:01         ` Stefan Priebe
2012-07-01 21:13           ` Mark Nelson
2012-07-01 21:27             ` Stefan Priebe
2012-07-02  5:02               ` Alexandre DERUMIER
2012-07-02  6:12                 ` Stefan Priebe - Profihost AG
2012-07-02 16:51                   ` Gregory Farnum
2012-07-02 19:22                     ` Stefan Priebe
2012-07-02 20:30                       ` Josh Durgin
2012-07-03  4:42                         ` Alexandre DERUMIER
2012-07-03  4:42                         ` Alexandre DERUMIER
2012-07-03  7:49                         ` Stefan Priebe - Profihost AG
2012-07-03 15:31                           ` Sage Weil
2012-07-03 18:20                             ` Stefan Priebe
2012-07-05 21:33                               ` Gregory Farnum
2012-07-06  3:50                                 ` Alexandre DERUMIER
2012-07-06  8:54                                   ` Stefan Priebe
2012-07-06 17:11                                   ` Gregory Farnum
2012-07-06 18:09                                     ` Stefan Priebe - Profihost AG
2012-07-06 18:17                                       ` Gregory Farnum
2012-07-09 18:21                                         ` Stefan Priebe
2012-07-03 19:16                             ` Stefan Priebe
2012-07-02 13:19           ` Stefan Priebe - Profihost AG
2012-06-29 12:33 ` Stefan Priebe - Profihost AG

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=4FED8792.1090905@profihost.ag \
    --to=s.priebe@profihost.ag \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox