----- Original Message ---- > From: Marko Kreen <mark...@gmail.com> > To: Nick Mathewson <ni...@freehaven.net>; libevent-users@monkey.org > Sent: Wednesday, July 1, 2009 4:02:28 PM > Subject: Re: [Libevent-users] order of timers when attached inside a callback > > On 7/1/09, Nick Mathewson wrote: > > On Wed, Jul 01, 2009 at 01:05:33PM +0300, Marko Kreen wrote: > > > Also, although cached per-base tv_cache should already create some amount > > > of equal timeouts, this can be increased by rounding abs timeout values > > > to fixed granularity positions, depending how far in the future they are: > > > > > > 0.. 1s -> 1ms? > > > 1..10s -> 100ms > > > >10s -> 1s > > > > > > No, I think rounding is a pretty bad idea. There are people who > > actually care about timing accuracy: if they ask for 10.4 seconds and > > we give them 10 seconds, they won't be amused.
[snip] > > But if anyone schedules for 10.4 sec and expects to be called > after exactly 10400000 microseconds - I would call him silly... > The timer are already delayed and the more events you have the > more they can be. Call me silly, but I expect libevent to at least try for 10400000 microseconds, and it appears to do a reasonable job even with a large number of timers. If it happened after 10000000 microseconds, I would indeed not be amused. :) Larry _______________________________________________ Libevent-users mailing list Libevent-users@monkey.org http://monkeymail.org/mailman/listinfo/libevent-users
