alexeykupershtokh / node-perf-time Goto Github PK

Each time we have to really re-calculate time value we can calculate difference since last time calculation. If it's more than some value (e.g. 2ms), then we should likely use lower rate in order to flush the cached value more often. Such timers will have more impact on performance but would be more accurate.

A good option for this is to bring in an "recommended accuracy" parameter. When the diff would exceed the recommended accuracy, we can set rate lower. This would allow automatically level sync cycle problems.

Also we could improve performance if the diff is < 1ms by making rate higher.