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 2003/04/25 20:01:48 UTC

DO NOT REPLY [Bug 12336] - wrong time in first "Sample -ms"

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=12336>.
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=12336

wrong time in first "Sample -ms"

mstover1@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From mstover1@apache.org  2003-04-25 18:01 -------
Yes, this is probably hotspot compile time + new object creation time and the
like.  Obviously, all samples are timed in the same way, but the first time
objects are created, connections setup, possibly code is just-in-time compiled,
etc.  

A good fix for this would be to allow a user to specify a "warm-up" period
during which data is not logged.  

A good workaround is to let the test run for long enough to discount the
abnormally high first sample.

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org