All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mark.nelson@inktank.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: Sage Weil <sage@inktank.com>,
	"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 10:06:23 -0600	[thread overview]
Message-ID: <509BD87F.1010107@inktank.com> (raw)
In-Reply-To: <509BD38B.8090200@profihost.ag>

On 11/08/2012 09:45 AM, Stefan Priebe - Profihost AG wrote:
> Am 08.11.2012 16:01, schrieb Sage Weil:
>> On Thu, 8 Nov 2012, Stefan Priebe - Profihost AG wrote:
>>> Is there any way to find out why a ceph-osd process takes around 10
>>> times more
>>> load on rand 4k writes than on 4k reads?
>>
>> Something like perf or oprofile is probably your best bet.  perf can be
>> tedious to deploy, depending on where your kernel is coming from.
>> oprofile seems to be deprecated, although I've had good results with
>> it in
>> the past.
>
> I've recorded 10s with perf - it is now a 300MB perf.data file. Sadly
> i've no idea what todo with it next.

Pour yourself a stiff drink! (haha!)

Try just doing a "perf report" in the directory where you've got the 
data file.  Here's a nice tutorial:

https://perf.wiki.kernel.org/index.php/Tutorial

Also, if you see missing symbols you might benefit by chowning the file 
to root and running perf report as root.  If you still see missing 
symbols, you may want to just give up and try sysprof.

>
>>   would love to see where the CPU is spending most of it's time.  This is
>> on current master?
> Yes
>
>>  I expect there are still some low-hanging fruit that
>> can bring CPU utilization down (or even boost iops).
> Would be great to find them.
>
> 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-08 16:06 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 [this message]
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

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=509BD87F.1010107@inktank.com \
    --to=mark.nelson@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=s.priebe@profihost.ag \
    --cc=sage@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 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.