> 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.
I have it looping 100 times, but I going to try to do stability tests by running it forever and see how long it stays up for. >> >> 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. I was only using it as a ball park figure. I was wondering if I could handle a 2MBit internet connection. Which (assuming they use 1000KBit = 1MBit - yeah I know it should be 1024, but look at hard drives - and 8Bit = 1 Byte) is 250KBytes / Second. If I want each connection to have at least 2KBytes/sec I can have 250/2 = 125 concurrent connections. Depending on user usage patterns (I have no idea on this) we can have 1,250 users logged in at once. This simple test handled over 1,000 request per second. Therefore it seems highly likely that it could handle 125 concurrent requests. Can anyone give me there experience with the amount of bandwidth needed. I live in Australia and it is very hard to get over 2MBit without having a large company wallet. Thanks, Cameron Zemek -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
