> Or an easier option might be having two scripts, one normal & one with > timeouts, and running them both at the same time?
When implementing a timeout driven approach, using those two groups is a must, because the timeout group *will* generate a large number of errors, and thus screw up your stats. You want to know how many requests "really" timeout, i.e. when having browser-like timeout values. Also, you want to know just how slow your servers get, and that is what a second thread group will have to find out. It will be much smaller (say 15-25 threads) in my upcoming test plan. Still, whether all of this makes any sense in the end remains to be seen. Cheers, Felix --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
