On 6 April 2011 10:55, Paul Thomas wrote:
> 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?
You can time blocking calls by instrumenting
twisted.python.log.callWithContext and you could try writing the
timing in
On Wed, Apr 6, 2011 at 1:35 PM, Laurens Van Houtven <_...@lvh.cc> wrote:
> Hi!
>
>
> 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 Twi
On 06/04/11 13:19, Itamar Turner-Trauring wrote:
> On Wed, 2011-04-06 at 10:55 +0100, Paul Thomas wrote:
>> 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 li
On Wed, 2011-04-06 at 10:55 +0100, Paul Thomas wrote:
> 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 ev
Hi!
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
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.
Should I just h
