summaryrefslogtreecommitdiffstats
path: root/doc/rados/troubleshooting/cpu-profiling.rst
blob: 159f7998dcb99a241138bcadab48abac3a147d3b (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
===============
 CPU Profiling
===============

If you built Ceph from source and compiled Ceph for use with `oprofile`_
you can profile Ceph's CPU usage. See `Installing Oprofile`_ for details.


Initializing oprofile
=====================

The first time you use ``oprofile`` you need to initialize it. Locate the
``vmlinux`` image corresponding to the kernel you are now running. :: 

	ls /boot
	sudo opcontrol --init
	sudo opcontrol --setup --vmlinux={path-to-image} --separate=library --callgraph=6


Starting oprofile
=================

To start ``oprofile`` execute the following command:: 

	opcontrol --start

Once you start ``oprofile``, you may run some tests with Ceph. 


Stopping oprofile
=================

To stop ``oprofile`` execute the following command:: 

	opcontrol --stop
	
	
Retrieving oprofile Results
===========================

To retrieve the top ``cmon`` results, execute the following command:: 

	opreport -gal ./cmon | less	
	

To retrieve the top ``cmon`` results with call graphs attached, execute the
following command:: 

	opreport -cal ./cmon | less	
	
.. important:: After reviewing results, you should reset ``oprofile`` before
   running it again. Resetting ``oprofile`` removes data from the session 
   directory.


Resetting oprofile
==================

To reset ``oprofile``, execute the following command:: 

	sudo opcontrol --reset   
   
.. important:: You should reset ``oprofile`` after analyzing data so that 
   you do not commingle results from different tests.

.. _oprofile: http://oprofile.sourceforge.net/about/
.. _Installing Oprofile: ../../../dev/cpu-profiler