This document summarizes the configuration we used to perform load-testing for the BusyDatabase 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 |
| SQL Tier | P3 |
| Max Pool Size | 4000 |
The load test project included two webtests, each invoking an HTTP GET operation.
The URLs used were:
- http://yourservice.cloudapp.net/toomuchprocsql/get/{orderid}
- http://yourservice.cloudapp.net/lessprocsql/get/{orderid}
Replace yourservice with the name of your cloud service, and replace {orderid} with an order number generated by using the Generate Random Integer plugin.
The project also included two load tests, one for each web test. Both 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 | 50 |
| Step Duration | 30s |
| Step Ramp Time | 0s |
| Step User Count | 1 |
| Test Duration | 30 minutes |
| Test Warm Up | 30 seconds |
The load test for the http://yourservice.cloudapp.net/toomuchprocsql/get/{orderid} web test generated the following results:
The load test for the http://yourservice.cloudapp.net/lessprocsql/get/{orderid} web test generated the following results:
