On 23/01/2003 6:49 PM, "Cameron Zemek" <[EMAIL PROTECTED]> wrote:
> On Thu, 2003-01-23 at 17:37, Scott Eade wrote: >> On 23/01/2003 6:18 PM, "Cameron Zemek" <[EMAIL PROTECTED]> wrote: >> >>> On Thu, 2003-01-23 at 17:02, Scott Eade wrote: >>>> 1. Set a ramp-up figure of greater than 0s - to start 1 thread per second >>>> use 100s. >>> >>> Then the thread finishes before the next one starts. I want 100 threads >>> running at the same time. >> How short are your scripts? I would imagine the scripts would have to be >> more than 1 second long (including delays) in order to be an accurate >> reflection of real users utilizing the system. I also meant to say that you can make your script run longer by increasing the number of loops. If you only have a single request in your script then set the loop count to something like 500. > > Short, I was load testing the server not an application. I was > requesting a 94byte HTML document (Hello World). I got an average of > 73ms which is less then a second. The jmeter-server script was running > on the web server. Is this okay? How does remote testing with JMeter > work?? I am not quite sure what you are hoping to achieve by testing using a dummy document like you are. If all you are trying to do is throw load at a server then fine, but don't quote the response times as anything meaningful (in your example the web server will most likely have the page cached and will serve it up with pretty much no processing). This is nothing like how a real application would behave and it would be a big mistake IMHO to attempt to relate your test results with how an application might perform. For some basic information on remote testing see: http://nagoya.apache.org/wiki/apachewiki.cgi?JMeterFAQ HTH, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au .Mac Chat/AIM: seade at mac dot com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
