Post: #19

probably it happen because the main internal timer on sphere (including <SERV.TIME>) is based on CPU clocks (ticks per second) instead system time (miliseconds)

system time is a timestamp based on real calendar time, but system ticks is a timestamp based on CPU clocks since latest system restart, which does the job if you don't need much precision, but if you need it (like in topic example) it won't have a perfect timer because every CPU has a difference of 10~20ms between each tick

so maybe there's nothing left to do in this case, there's no way to get perfect timers or <SERV.TIME> values unless change the sphere main internal timer to use system time (miliseconds) instead CPU clock (ticks per second). It's not difficult to change it, but honestly I don't know if this will bring any advantage since ~maybe~ this could make sphere consume more CPU usage