[Twisted-Python] finding out what's blocking the reactor

[Glyph]

> On May 13, 2019, at 7:26 AM, Chris Withers <chris at withers.org> wrote:
> 
> Hi All,
> 
> On some busy instances of the app I'm working with/on, we see websocket connections being dropped due to not ping/ponging in time, I'm fairly sure this is as a result of some user-written callbacks blocking the reactor for long periods of time (seconds...).
> 
> What's the best way to debug a twisted application to find out what's blocking the reactor?

I don’t know about “the best”, but I’ve had some success with https://vmprof.readthedocs.io/en/latest and https://github.com/ggreer/twisted_hang depending on what you’re looking for.

Let us know if these work out!

-g


-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/twisted-python/attachments/20190513/89ad3a50/attachment-0002.html>