That reminds me -
Tests I've done on Windows show that nanoTime() drifts considerably
when compared with currentTimeMillis(), i.e. its clock does not appear
to run at the same rate.
Here's a simple test you can run:
public class NanoDrift {
public static void main(String[] args) throws
I've talked with BEA's JRockit team in the past regarding the
differences in Nano time on different platforms.
Given these issues, using nano time in JMeter is difficult at best.
From what I am told by Henrik stahl, making nano time reliable and
performant isn't trivial, so using it to measure
On 31 March 2011 19:41, Ben Cuthbert ben_cuthb...@yahoo.co.uk wrote:
All
I have been looking over the code in the JUnitSampler code under the jmeter
source.
I would like to make a change to use nanoTime() rather than milliseconds.
Why?
I can see in the AnnotatedTestCase there is an
All
I have been looking over the code in the JUnitSampler code under the jmeter
source.
I would like to make a change to use nanoTime() rather than milliseconds.
I can see in the AnnotatedTestCase there is an elapsed time. But I can't see
how it
is returned to a results table. Any ideas?
