Comments on: How to clock routines which (should) go faster than 1 sec http://www.fourone.se/blog/2008/03/28/how-to-clock-routines-which-should-go-faster-than-1-sec/ Dynamics AX development blog Thu, 09 Sep 2010 18:20:06 +0000 http://wordpress.org/?v=2.3.1 By: Henrik Laurell http://www.fourone.se/blog/2008/03/28/how-to-clock-routines-which-should-go-faster-than-1-sec/#comment-100 Henrik Laurell Fri, 28 Mar 2008 16:52:25 +0000 http://www.fourone.se/blog/2008/03/28/how-to-clock-routines-which-should-go-faster-than-1-sec/#comment-100 The getTickCount method is of course much better. Thanks for the tip, I will add an update to this later with that included. /Henrik The getTickCount method is of course much better. Thanks for the tip, I will add an update to this later with that included.

/Henrik

]]> By: Björn http://www.fourone.se/blog/2008/03/28/how-to-clock-routines-which-should-go-faster-than-1-sec/#comment-99 Björn Fri, 28 Mar 2008 16:44:34 +0000 http://www.fourone.se/blog/2008/03/28/how-to-clock-routines-which-should-go-faster-than-1-sec/#comment-99 Interesting use of setTimeOut(). But with all function calls to updateTimer, I think there's still a rather large overhead and measuring error, hence the unreliability you noticed. Have you considered using WinAPI::getTickcount()? It's a wrapper around the Windows GetTickCount function which returns the number of milliseconds the system has been running. It's what the Timer class in 3.0 uses. Interesting use of setTimeOut(). But with all function calls to updateTimer, I think there’s still a rather large overhead and measuring error, hence the unreliability you noticed.

Have you considered using WinAPI::getTickcount()? It’s a wrapper around the Windows GetTickCount function which returns the number of milliseconds the system has been running. It’s what the Timer class in 3.0 uses.

]]>