wassname/ray
1
0
Fork 0
mirror of https://github.com/wassname/ray.git synced 2026-07-04 04:44:43 +08:00
Code Issues Packages Projects Releases Wiki Activity

Add gdb stack dump command to docs (#12147)

Browse Source 
* ZZ

* pid

* Update doc/source/profiling.rst

Co-authored-by: Stephanie Wang <swang@cs.berkeley.edu>

* Update profiling.rst

Co-authored-by: Stephanie Wang <swang@cs.berkeley.edu>
This commit is contained in:
Eric Liang
2020-11-19 16:02:11 -08:00
committed by GitHub
parent 67544992b5
commit dfc796b8ec
1 changed files with 15 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/source/profiling.rst
+15 -2
View File
@@ -1,8 +1,21 @@
Profiling for Ray Developers
============================
This document details, for Ray developers, how to use ``pprof`` to profile Ray
binaries.
This document details, for Ray developers, how to analyze Ray performance.
Getting a stack trace of Ray C++ processes
----------------------------------------
You can use the following GDB command to view the current stack trace of any
running Ray process (e.g., raylet). This can be useful for debugging 100% CPU
utilization or infinite loops (simply run the command a few times to see what
the process is stuck on).
.. code-block:: shell
sudo gdb -batch -ex "thread apply all bt" -p <pid>
Note that you can find the pid of the raylet with ``pgrep raylet``.
Installation
------------