zuul
/
zuul
Code Issues Proposed changes

Document usage of yappi profiler 

ff4eeec introduced support for yappi, a python profiler, which is used
when generating stack dumps (via SIGUSR2).  The commit forgot to update
the related documentation.

Change-Id: Iee1d680cf7b2df4c702666aaf778991c696c3274
This commit is contained in:
Antoine Musso 2014-06-04 09:54:24 +02:00
parent 6c3b76ab88
commit d0f06265e0
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/source/zuul.rst
View File

@ -1045,3 +1045,10 @@ recheck changes for the gate and check pipelines respectively::
If you send a SIGUSR2 to the zuul-server process, Zuul will dump a stack
trace for each running thread into its debug log. This is useful for
tracking down deadlock or otherwise slow threads.
When `yappi <https://code.google.com/p/yappi/>`_ (Yet Another Python
Profiler) is available, additional functions' and threads' stats are
emitted as well. The first SIGUSR2 will enable yappi, on the second
SIGUSR2 it dumps the information collected, resets all yappi state and
stops profiling. This is to minimize the impact of yappi on a running
system.