I am using siege to do the testing: siege -c 25 -b -t30s http://woooooooords.com/
from http://www.joedog.org/index/siege-home :D On Mon, Aug 2, 2010 at 1:45 PM, Mark Wieder <[email protected]> wrote: > Andre- > > Monday, August 2, 2010, 9:09:39 AM, you wrote: > > > Pierre, > > > I've just run 25 concurrent clients for 30 seconds against > > wooooooooords.comand no request failed. The report is as follow: > > One thing to watch for in doing load testing is that unless you're > using multiple machines for the test, you're stress-testing the client > machine as well as the server. In other words, you're limited by the > weakest point in your system - if your client machine starts to hiccup > it's almost indistinguishable from problems with the server, and > threading issues on the client will affect the results as much as > threading issues on the server. The only way to get meaningful results > from load-testing a server is to use multiple client machines. If you > could post your test code somewhere maybe more of us could run > simultaneous tests against the server for a distributed attack. > > -- > -Mark Wieder > [email protected] > > _______________________________________________ > use-revolution mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution > -- http://www.andregarzia.com All We Do Is Code. _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
