Hi!<br><br><br>No guarantee it's an optimal solution, but when I wanted to inspect a running process (which sounds like what you're doing), I had a pretty good time with manhole. (If you're not familiar with that: it's in Twisted Conch, and it's basically just a way to SSH in to a running box and get a REPL).<br>
<br>In that REPL, you can of course do things like inspect the running reactor :-)<br><br><br>cheers<br>lvh<br><br><div class="gmail_quote">On Wed, Apr 6, 2011 at 11:55 AM, Paul Thomas <span dir="ltr"><<a href="mailto:spongelavapaul@googlemail.com">spongelavapaul@googlemail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I have a reactor which is getting busier over time and I'd like to find out where the cycles are going. Using the profiler isn't really practical on a server running for days, so I'd like to instrument the reactor to show me which I/O events are taking the longest to deal with.<br>
<br>
Should I just hack into the reactor somewhere? Or is there something sitting in a library I haven't seen that will help with this?<br>
<br>
Paul.<br>
<br>
_______________________________________________<br>
Twisted-Python mailing list<br>
<a href="mailto:Twisted-Python@twistedmatrix.com">Twisted-Python@twistedmatrix.com</a><br>
<a href="http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python" target="_blank">http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>cheers<div>lvh</div><br>