From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: ceph-osd cpu usage
Date: Thu, 15 Nov 2012 11:56:37 +0100 [thread overview]
Message-ID: <50A4CA65.2030508@profihost.ag> (raw)
[-- Attachment #1: Type: text/plain, Size: 368 bytes --]
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
[-- Attachment #2: out.pdf --]
[-- Type: application/pdf, Size: 19302 bytes --]
next reply other threads:[~2012-11-15 10:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 10:56 Stefan Priebe - Profihost AG [this message]
2012-11-15 11:18 ` ceph-osd cpu usage Alexandre DERUMIER
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=50A4CA65.2030508@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