[Twisted-Python] LoopingCall at a non-idling reactor

Phil Mayers p.mayers at imperial.ac.uk
Mon Jul 20 06:52:43 EDT 2009

> I know what you mean.  If you trawl through my really old blog posts
> (I think the one I'm thinking of is on livejournal, but I can't find
> it quickly) you'll see that I've thought about this before.  The two
> main deterrents to changing the reactor to be a set of abstract
> "events" placed into a queue by event handlers rather than a  loop
> that just calls everything immediately are:
>  1) it might be slower, since it's extra code being run for every event, and

I wonder if wrapping one of the C event libraries and doing the bulk of 
the work in there would ameliorate that aspect.

>  2) it's a massive amount of work to actually implement it :).
> You could help out with #1 by implementing something and measuring it,
> and you can help out with #2 by just implementing it and letting
> someone else measure it :).

Fascinating though the topic is, I very much doubt I'll have any time to 
even look at it.

That said; is there a reactor "performance" test?

More information about the Twisted-Python mailing list