Postby ConvertFromOldNGs » Fri Aug 07, 2009 11:42 am
by Craig Shearer >> Mon, 2 Aug 1999 23:44:14 GMT
Hmmm interesting....
Perhaps it's just the thrill of a new release Carl!
However, I note from the release notes that there was a 1mS timer that fired continously resulting in some overhead...
"Note In a JADE 4 support release, the default granularity of the Application::clock method was reduced from the default 10mS to 1mS.
However, due to the way the Windows timer on which it was based is implemented, this incurred an overhead where an internal operating system interrupt timer fired continuously after a JADE node started. In JADE release 5.0, the granularity of the Application::clock method has reverted to 10mS, but for a 1mS accuracy timer you should now use the Application::relativeMachineTime method."