Generally speaking, in order to handle a large pool of threads and be able to scale the load, most loadtesting is done at the protocol (HTTP) level, not using full blown browser based clients.
Since most load is not from simple page hits against static or cached pages, you need to actually be interacting with the server as would a large number of unique users. Most decent webservers can serve cached copies of a static page until the pipe saturates without overloading the server or the back end. So having 200 users doing the same search, doesn't create the load you need. So what you need is a system where thread to use its own unique data, so you can simulate a hundred different users, shopping for 80-100 different items, or doing different searches or whatever. (and 100 is just to start, a true loadtest often simulates interacting with many thousand users over a period of an hour or so) While I might use Watir to conduct a functional test DURING a loadtest, I would not use it to apply the load. Despite the existence of the example, I personally would not do loadtesting with watir. I'd use something like the loadtesting tool in VS2010, Jmeter, or if you can afford it, Loadrunner. (which one would work best and provide the best bang for the buck depends on your server environment) On Mar 11, 10:30 am, "[email protected]" <[email protected]> wrote: > Hi, > > to see there are realy diffrent thread that are running change : > ...("Thread #{i} executed... > by > ...("Thread #{Thread.current} executed ... > > in log file information for loadtester.rb which can be download here : > > http://wiki.openqa.org/display/WTR/Re-Usable+Load+Testing+Example > > best regards, > plebailly -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. [email protected] http://groups.google.com/group/watir-general [email protected]
