[Twisted-Python] Accurate delays in callLater
gsakkis at eden.rutgers.edu
Thu Jun 23 12:29:30 EDT 2005
I'm using twisted for a realtime simulation and I'm calling
reactor.callLater() for scheduling actions to be performed after a fixed
short delay (~60msec). However, if there is a cpu-intensive procedure
running in the meantime, the timer for the scheduled call may expire much
later, an order of magnitude or more if the procedure takes too much time.
Is this to be expected in general ? If not, does this may have to with the
delay being too short or the cpu-intensive procedure being mainly run in
an extension module ? Finally, is there a way to force the required delay
(with a tolerance of a few msec) ?
Thanks for any insight,
More information about the Twisted-Python