Load tests timings : rounded to milliseconds?
I'm load testing my services on pretty quick new hardware. Typically the web service request elapsed times on the server are in the 1-2 millisecond range.
However, soapUI load test runner (command line version, 2.5.1) appears to be rounding all the response times to the nearest millisecond (I assume).
It reports an average elapsed time per request of less than the time that the server records to process the request. soapUI appears to be recording a time of 1ms for each request (and occasionally 2ms), hence an average just over 1ms. The server accurately records the requests as averaging about 1.72ms. I've double checked my server code - it looks correct.
In the soapUI manual there is a section comparing JMeter to soapUI. It specifically notes that soapUI uses System.nanoTime() rather than System.currentMillis(), but it would appear that it may later round these values to milliseconds.
Can anyone confirm that this is the case?
However, soapUI load test runner (command line version, 2.5.1) appears to be rounding all the response times to the nearest millisecond (I assume).
It reports an average elapsed time per request of less than the time that the server records to process the request. soapUI appears to be recording a time of 1ms for each request (and occasionally 2ms), hence an average just over 1ms. The server accurately records the requests as averaging about 1.72ms. I've double checked my server code - it looks correct.
In the soapUI manual there is a section comparing JMeter to soapUI. It specifically notes that soapUI uses System.nanoTime() rather than System.currentMillis(), but it would appear that it may later round these values to milliseconds.
Can anyone confirm that this is the case?
