timer: All configuration of granularity

[sdroege]

Currently the timer granularity is always 1ms. It would be nice to be able to configure this, to be able to have a higher granularity < 1ms, or what is needed in my case, a lower one (e.g. 20ms).

My use-case is to batch process timers: everything that is to be emitted in those e.g. 20ms should be handled at once, instead of waking up the thread many times during those 20ms and cause more context switches, CPU usage and power consumption.

Alternatively, some API to schedule timers with a specific granularity (like e.g. in GLib g_timeout_add_seconds) would be nice. So that e.g. all timers that are scheduled with 20ms granularity will be triggered at the same time, all timers with 1s granularity at the same time, etc.

[carllerche]

One option would be to only set timeouts at 20ms granularity. In that case, the thread shouldn't have to wake up? Since everything is deadline based, it should be possible to ensure that timeouts get set in 20ms increments. Does something like this work?

[sdroege]

Would that ensure that timers are always at 20ms boundaries, i.e. the absolute difference between any two timers' "trigger times" is always an integer multiple of 20ms? Then that would work, yes

[carllerche]

Closing due to inactivity.

[jonhoo]

See also tokio-os-timer for finer-grained timers.