DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=44374>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44374 Summary: Constant Throughtput Timer Granularity is too coarse Product: JMeter Version: 2.3.1 Platform: Sun OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: Main AssignedTo: jmeter-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] Trying to run test with constant throughput higher than 60000 executions per minute leads to uncontrolled throughtput increase. It happens because of millisecond level of delay granularity and due to usage of System.currentTimeMillis() calls for delay calculations. Because in one minute there are only 60 000 milliseconds and due to integer arithmetics for delay calculation, delay() method always returns 0 if throughput is greater than 60000 samples per minute. However, nowadays it is not unusual to have tens of millions executions per hour on SMP systems. I am testing Telecommunication platform which intended to handle 50-60 milllions calls per hour. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
