I have now had a look at your soapUI TestCase. The TestCase is fetching username and password from a DataSource and then doing a single SOAP Request plus two basic assertions.
The best way is probably to do as we've discussed: Run the TestCase via a soapUI Runner and distribute this to agents if needed. Note that the actual data sources (the CSV or XLS files) won't be distributed automatically, so you have to put them in the same folder on all agents. Also note that the current Amazon AMI seem to have disappeared from the list of public Amazon AMIs. As we're focusing all our efforts on loadUI 1.5 right now, we won't reconstruct an AMI for loadUI 1.0.1 but instead encourage you to wait for loadUI 1.5 which will have a fresh AMI. LoadUI 1.5 is scheduled for mid-May (Beta) and June (Final/Stable).
With that being said, I'm not so sure that using Amazon agents is what you really need for this scenario. Two things to consider:
- 5000 concurrent requests is extreme for regular requests. The only web service coming close to this kind of load is Google's search engine.
- A fairly new computer running loadUI can handle 5000 concurrent requests. The most common reason for agent distribution is network limitations, rather than CPU performance. I would try reaching the desired load (alternatively the load that makes the web server failing to deliver) first by just using loadUI in Local Mode, then distributed to a couple of inhouse agents. Just in case your web application breaks way before your outbound network connection... Then I would go for Amazon agents, if needed.
Regards!
/Henrik
eviware.com