[ajeet_dhaliwal]

I did this a couple of years ago to load test and stress a public web service. We used the results to determine how many servers to launch with and how many requests per second we would be able to handle with adequate response times. We were also able to measure improvements due our optimizations.

At the time, due to the company I worked at it, and because the service itself was a C#/.NET service it made sense to be writing tests in C#/.NET using Microsoft's Visual Studio Test Framework. Visual Studio, I think starting from the 2013 version has a built in load testing capability that integrates with Azure (you have to create an account) that will automatically spin up instances temporarily for you in order to load test the endpoint(s) you specify using the parameters you provide in VS created web tests. It worked rather well for us. I understand this is highly specific to our use case but if you didn't know this existed it's something to be aware of.

[Bladtman]

I was not aware of that, thanks. Knowing how many requests you can handle before you need to upscale must be nice. Would you do something like that again on a different project?