From: "Piotr Dałek" <branch@predictor.org.pl>
To: Victor Denisov <vdenisov@mirantis.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Questions about profiling ceph
Date: Tue, 22 Nov 2016 21:00:37 +0100 [thread overview]
Message-ID: <20161122200037.GD26997@predictor> (raw)
In-Reply-To: <CA+hcxJQQHfhGBHZkfcwn4m3Zfxwh7dPXK=tyVg1d5rw26WNp3g@mail.gmail.com>
On Tue, Nov 22, 2016 at 11:42:48AM -0800, Victor Denisov wrote:
> Hello ceph developers,
>
> I'm learning how to profile ceph and came across this page:
> http://docs.ceph.com/docs/giant/rados/troubleshooting/cpu-profiling/
>
> The page suggests to use oprofile. I compiled oprofile version
> 1.1.0(http://oprofile.sourceforge.net/faq/), but it doesn't have
> opcontrol binary.
>
> Am I doing something wrong? Is it an outdated procedure for profiling?
> Is there a newer one?
Well, they actually noted (in the faq you linked) that opcontrol is a
legacy tool. And the cpu profiling guide is for "Giant" Ceph release
(also quite legacy).
Anyway, operf + opreport tandem is sufficient for me and I'm sure it
will be enough for you.
--
Piotr Dałek
branch@predictor.org.pl
http://blog.predictor.org.pl
next prev parent reply other threads:[~2016-11-22 19:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 19:42 Questions about profiling ceph Victor Denisov
2016-11-22 20:00 ` Piotr Dałek [this message]
2016-11-22 23:05 ` Mark Nelson
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=20161122200037.GD26997@predictor \
--to=branch@predictor.org.pl \
--cc=ceph-devel@vger.kernel.org \
--cc=vdenisov@mirantis.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.