This document summarizes the configuration we used to perform load-testing for the ImproperInstantiation anti-pattern. You should also read about our general approach to deployment and load testing.
| Option | Value |
|---|---|
| Compute | Cloud Service |
| VM Size | Large |
| Instance Count | 1 |
The load test project included four webtests, each invoking an HTTP GET operation.
The URLs used were:
- http://yourservice.cloudapp.net/api/newhttpclientinstanceperrequest/{ProductID}
- http://yourservice.cloudapp.net/api/singlehttpclientinstance/{ProductID}
- http://yourservice.cloudapp.net/api/newserviceinstanceperrequest/{ProductID}
- http://yourservice.cloudapp.net/api/singleserviceinstance/{ProductID}
Replace yourservice with the name of your cloud service, and replace {ProductID} with an product ID generated by using the Generate Random Integer plugin.
The project also included four load tests, one for each web test. All load tests were run against a single deployment but at different times, using the following parameters:
| Parameter | Value |
|---|---|
| Initial User Count | 1 |
| Maximum User Count | 1000 |
| Step Duration | 60s |
| Step Ramp Time | 0s |
| Step User Count | 100 |
| Test Duration | 10 minutes |
| Test Warm Up | 30 seconds |
The load test for the http://yourservice.cloudapp.net/api/newhttpclientinstanceperrequest/{ProductID} web test generated the following results:
The load test for the http://yourservice.cloudapp.net/api/singlehttpclientinstance/{ProductID} web test generated the following results:
The load test for the http://yourservice.cloudapp.net/api/newserviceinstanceperrequest/{ProductID web test generated the following results:
The load test for the http://yourservice.cloudapp.net/api/singleserviceinstance/{ProductID} web test generated the following results:
