2014-09-29 11:00 GMT+02:00 Saúl Ibarra Corretgé <[email protected]>: > Also, on top the above, creating and processing a timer requires 3 > syscalls: timerfd_create, timerfd_gettime and read vs 0 if we keep the > min-heap.
Given that UV periodic timer is just an API sugar over the regular timer, would not make sense that the loop execution time is taken into account when setting the next timer period? This is: - Run periodic timer with interval 100 ms. - First loop iteration takes 15 ms. - Somehow libuv knows that and set the timer next period on 85 ms. Just wondering. -- Iñaki Baz Castillo <[email protected]> -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
