You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2002/09/04 22:18:37 UTC
DO NOT REPLY [Bug 12314] New: -
Rationalize Timer GUIs
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12314>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12314
Rationalize Timer GUIs
Summary: Rationalize Timer GUIs
Product: JMeter
Version: 1.7.3
Platform: All
OS/Version: All
Status: NEW
Severity: Minor
Priority: Other
Component: Main
AssignedTo: jmeter-dev@jakarta.apache.org
ReportedBy: eric_97@pobox.com
A U.I. nit: The inputs to the two styles of random timers have different
semantics. In the Gaussian timer, the Delay Offset provides a "center point"
around which the delays cluster. In the uniform timer, it provides a strict
minimum. They should both work the same way.
My preference would be for the Gaussian's center-point style. What one wants to
say, in all of the timers, is "delay for X, plus-or-minus a random delta `tuned'
by Y". Gaussian lets me say that directly (so does the Constant timer,
trivially; the delta is always 0). But uniform makes me do some arithmetic to
get there.
The uniform delay calculation could be something like this:
delayTime = this.delay + (nextRandom() * 2 - 1) * this.range;
With this change, the "Constant Delay Offset" in both random timers could be
relabelled "Average Delay", a much less cryptic description, IMO.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>