Add "ray timeline" command to auto-dump Chrome trace for the current Ray instance (#4239)

This commit is contained in:
Eric Liang
2019-03-05 16:28:00 -08:00
committed by Robert Nishihara
parent 4cf2c9ecb8
commit 78ad9c4cbb
4 changed files with 60 additions and 1 deletions
+8
View File
@@ -57,3 +57,11 @@ The Ray Command Line API
.. click:: ray.scripts.scripts:get_head_ip
:prog: ray get_head_ip
:show-nested:
.. click:: ray.scripts.scripts:stack
:prog: ray stack
:show-nested:
.. click:: ray.scripts.scripts:timeline
:prog: ray timeline
:show-nested:
+2 -1
View File
@@ -136,4 +136,5 @@ try setting ``OMP_NUM_THREADS=1``. Similarly, check configured system limits wit
If you encounter out-of-memory errors, consider setting ``redis_max_memory`` and ``object_store_memory`` in ``ray.init()`` to reduce memory usage.
For debugging unexpected hangs or performance problems, you can run ``ray stack`` to dump
the stack traces of all Ray workers on the current node. This requires py-spy to be installed.
the stack traces of all Ray workers on the current node, and ``ray timeline`` to dump
a timeline visualization of tasks to a file.