<div dir="ltr">Hi Henning<br><br>yes a 1s interval timer registered through the timer API. I then count the ticks corresponding to 5 mins (current ticks + (5*60)). At the end the stopwatch (wallclock) reads 5min and 20 secs. My question is what the impact on for example the Dailog module which relies on these timers for timeouts, etc. A timeout on a dialog of for example 3600 will be horribly out.<br>
<br>Cheers<br>Jason<br><br><div class="gmail_quote">On Wed, Sep 24, 2008 at 11:22 AM, Henning Westerholt <span dir="ltr"><<a href="mailto:henning.westerholt@1und1.de">henning.westerholt@1und1.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="Wj3C7c">On Tuesday 23 September 2008, Jason Penton wrote:<br>
> I was testing the Kamailio timer API today and noticed some inaccuracy and<br>
> wondered if this was known?<br>
><br>
> If I register a 1 second interval timer and count the ticks I get a<br>
> discrepancy of almost 20s per 5 minutes inaccuracy. What is the feeling on<br>
> this?<br>
<br>
</div></div>Hi Jason,<br>
<br>
do you mean if you register a 1 second interval timer, then after 5 minutes it<br>
goes 20 seconds wrong? Wrong to the wallclock, or wrong with regards to<br>
another timer(s)?<br>
<br>
20 seconds inaccuracy on 5 minutes is too much. For comparision, we use a<br>
simple sleep based timer approach for some maintainance stuff in older code,<br>
here we get about 1 seconds inaccuracy per 2 hours with a 10 seconds<br>
interval.<br>
<br>
Cheers,<br>
<font color="#888888"><br>
Henning<br>
</font></blockquote></div><br></div>