projects / ceph.git / blame
| Commit | Line | Data |
|---|---|---|
| 7c673cae FG |
1 | ===================== |
| 2 | Installing Oprofile | |
| 3 | ===================== | |
| 4 | ||
| 5 | The easiest way to profile Ceph's CPU consumption is to use the `oprofile`_ | |
| 6 | system-wide profiler. | |
| 7 | ||
| 8 | .. _oprofile: http://oprofile.sourceforge.net/about/ | |
| 9 | ||
| 10 | Installation | |
| 11 | ============ | |
| 12 | ||
| 13 | If you are using a Debian/Ubuntu distribution, you can install ``oprofile`` by | |
| 14 | executing the following:: | |
| 15 | ||
| 16 | sudo apt-get install oprofile oprofile-gui | |
| 17 | ||
| 18 | ||
| 19 | Compiling Ceph for Profiling | |
| 20 | ============================ | |
| 21 | ||
| 22 | To compile Ceph for profiling, first clean everything. :: | |
| 23 | ||
| 24 | make distclean | |
| 25 | ||
| 26 | Then, export the following settings so that you can see callgraph output. :: | |
| 27 | ||
| 28 | export CFLAGS="-fno=omit-frame-pointer -O2 -g" | |
| 29 | ||
| 30 | Finally, compile Ceph. :: | |
| 31 | ||
| 32 | ./autogen.sh | |
| 33 | ./configure | |
| 34 | make | |
| 35 | ||
| 36 | You can use ``make -j`` to execute multiple jobs depending upon your system. For | |
| 37 | example:: | |
| 38 | ||
| 39 | make -j4 | |
| 40 | ||
| 41 | ||
| 42 | Ceph Configuration | |
| 43 | ================== | |
| 44 | ||
| 45 | Ensure that you disable ``lockdep``. Consider setting logging to | |
| 46 | levels appropriate for a production cluster. See `Ceph Logging and Debugging`_ | |
| 47 | for details. | |
| 48 | ||
| 49 | .. _Ceph Logging and Debugging: ../../rados/troubleshooting/log-and-debug | |
| 50 | ||
| 51 | See the `CPU Profiling`_ section of the RADOS Troubleshooting documentation for details on using Oprofile. | |
| 52 | ||
| 53 | ||
| 54 | .. _CPU Profiling: ../../rados/troubleshooting/cpu-profiling |