On 9 November 2010 12:43, Andrej van der Zee <[email protected]> wrote: > Hi, > > We experienced that JMeter's timestamps get out-of-sync with the > system clock. Is it true that JMeter does not read the system clock, > but uses performance counters or something like that to calculate the > difference between the start time and the current time? If so, can I > overwrite this behavior and force JMeter to use the system clock > instead? The platform is Windows XP.
JMeter saves both System.currentTimeMillis() and System.nanoTime() at the start of a run. It then uses System.nanoTime() differences to arrive at the current time with a resolution of 1ms. System.nanoTime() Javadoc says "The value returned represents nanoseconds since some fixed but arbitrary time". If this is not true, or if the nanosecond clock is not very accurate, then of course the JMeter timestamps can drift. Are you running in a virtual environment? Some are known to have timer issues. There's no option to change the JMeter behaviour currently, but of course you can always edit the source, in this case org.apache.jmeter.samplers.SampleResult And you can raise a Bugzilla enhancement request to make the use of nanoTime optional. > Thank you, > Andrej > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
