All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre DERUMIER <aderumier@odiso.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: ceph-devel@vger.kernel.org
Subject: Re: ceph-osd cpu usage
Date: Thu, 15 Nov 2012 12:18:21 +0100 (CET)	[thread overview]
Message-ID: <7840e3d1-17b2-4618-ae1f-ff3dbdff71f6@mailpro> (raw)
In-Reply-To: <50A4CA65.2030508@profihost.ag>

cpu usage is same for read and write  ?


----- Mail original ----- 

De: "Stefan Priebe - Profihost AG" <s.priebe@profihost.ag> 
À: ceph-devel@vger.kernel.org 
Envoyé: Jeudi 15 Novembre 2012 11:56:37 
Objet: ceph-osd cpu usage 

Hello list, 

my main problem right now is that ceph does not scale for me (more vms 
using rbd). It does not scale as the ceph-osd is using all my CPU core 
all the time (8 cores) with just 4 SSDs. The SSDs are far away from 
being loaded. 

What is the best way to find out what the ceph-osd process is doing all 
the time? 

A gperf graph is attached. 

Greets, 
Stefan 
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-11-15 11:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-15 10:56 ceph-osd cpu usage Stefan Priebe - Profihost AG
2012-11-15 11:18 ` Alexandre DERUMIER [this message]
2012-11-15 12:19   ` Stefan Priebe - Profihost AG
2012-11-15 15:12     ` Mark Nelson
2012-11-15 16:09       ` Stefan Priebe
2012-11-15 16:52         ` Sage Weil
2012-11-15 19:44       ` Stefan Priebe
2012-11-15 15:14 ` Sage Weil
2012-11-15 15:30   ` Stefan Priebe - Profihost AG
2012-11-15 20:26   ` Stefan Priebe
2012-11-16  8:41     ` Alexandre DERUMIER
2012-11-16  9:11       ` 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=7840e3d1-17b2-4618-ae1f-ff3dbdff71f6@mailpro \
    --to=aderumier@odiso.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=s.priebe@profihost.ag \
    /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.