timer's problem for mushclient running on a cloud computer(VPN)

my mushclient is running on a remote cloud computer, I made a timer with interval of 3 seconds, but it found that the timer's next time running is remaining exceed 3 seconds, sometimes "next" showed 8s, even sometimes it's more than 20 seconds. What's cause the timer's interval automatically changed?



</timer>
<timer name="pfm" second="3.00" offset_second="0.00" send_to="10"
group="pfm" >
<send>hp</send>

Could it be related to this?

http://www.gammon.com.au/forum/?id=8159&reply=14#reply14

Timers are implemented using Windows timers which are a low priority event. Possibly your cloud computer is servicing other things (eg. comms) which is deferring it noticing the timer expiry.

If there is a lot of activity on the MUD you could possibly work around it by building in a time-elapsed check on a "catch-all" trigger, and using that to do things after a certain number of seconds elapses.