CEPH filesystem development
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Mark Nelson <mark.nelson@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: extreme ceph-osd cpu load for rand. 4k write
Date: Thu, 08 Nov 2012 16:45:54 +0100	[thread overview]
Message-ID: <509BD3B2.1040001@profihost.ag> (raw)
In-Reply-To: <509BC95F.5090904@inktank.com>

Am 08.11.2012 16:01, schrieb Mark Nelson:
> Hi Stefan,
>
> You might want to try running sysprof or perf while the OSDs are running
> during the tests and see where CPU time is being spent.  Also, how are
> you determining how much CPU usage is being used?

Hi Mark,

have a 300MB perf.data file and no idea what todo next ;-)

Stefan

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

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-07 20:41 extreme ceph-osd cpu load for rand. 4k write Stefan Priebe
2012-11-08 14:58 ` Stefan Priebe - Profihost AG
2012-11-08 15:01   ` Sage Weil
2012-11-08 15:45     ` Stefan Priebe - Profihost AG
2012-11-08 16:06       ` Mark Nelson
2012-11-08 21:27         ` Stefan Priebe
2012-11-08 21:50           ` Josh Durgin
2012-11-08 21:58             ` Mark Nelson
2012-11-08 22:06               ` Stefan Priebe
2012-11-08 22:31             ` Stefan Priebe
2012-11-09 10:09         ` Stefan Priebe - Profihost AG
2012-11-09 10:21           ` Stefan Priebe - Profihost AG
2012-11-09 21:21             ` Samuel Just
2012-11-09 21:34               ` Stefan Priebe - Profihost AG
2012-11-10 20:36                 ` Samuel Just
2012-11-10 20:37                   ` Samuel Just
2012-11-10 20:43                     ` Stefan Priebe
2012-11-10 20:42                   ` Stefan Priebe
2012-11-08 15:01   ` Mark Nelson
2012-11-08 15:45     ` Stefan Priebe - Profihost AG [this message]

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=509BD3B2.1040001@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=ceph-devel@vger.kernel.org \
    --cc=mark.nelson@inktank.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox