Summary: | Reduce overhead in calculating SampleResult#nanoTimeOffset | ||
---|---|---|---|
Product: | JMeter - Now in Github | Reporter: | Sebb <sebb> |
Component: | Main | Assignee: | JMeter issues mailing list <issues> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | ||
Priority: | P2 | ||
Version: | 2.5.1 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | All |
Description
Sebb
2011-12-14 17:57:13 UTC
Note: it looks like Thread.sleep() returns to the thread shortly after a clock transition (as might be expected). Calculating the nanoTime offset immediately afterwards should ensure more consistent values. With the current implementation - which may call currentTimeMills at any point in the clock cycle - the granularity of currentTimeMillis (generally 10ms-15ms) means that the offset can vary by that amount. URL: http://svn.apache.org/viewvc?rev=1215361&view=rev Log: Bug 52333 - Reduce overhead in calculating SampleResult#nanoTimeOffset Use a background thread to calculate the offset instead of doing it each sample Modified: jmeter/trunk/bin/jmeter.properties jmeter/trunk/src/core/org/apache/jmeter/samplers/SampleResult.java jmeter/trunk/test/src/org/apache/jmeter/samplers/TestSampleResult.java jmeter/trunk/xdocs/changes.xml jmeter/trunk/xdocs/usermanual/listeners.xml This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2679 |