Capacity testing is basically trying to break our application.
So, how do we break it?
Take the load formula and multiply it by a factor. For example if the load includes invoking 100 requests/sec, try interactively to multiply it by a constant (1,2,3…) factor starting with 2 and continue while you did not reach your capacity.
Run the test and wait for failed requests.
§ TIP: Set the test for run duration of at least 30 minutes.
If a request fails, check what the critical resource that caused it is.
§ TIP: A capacity can be caused by system resources or application related reasons. Usually it is caused by a certain system resource, such as Memory, Disk, CPU or Network. By indicating the resources that caused the capacity, we can recommend how to increase the capacity.
§ Generally speaking a failed request is a request that returns with an error code higher than 400.
§ TIP: In case you want to create a capacity for the current IIS configuration any request failure will result a capacity.
§ TIP: In case you want to create a capacity and ignore the current IIS configurations, insure that the failures are not resulted by those configurations such as connection limit or maximum queue length. The type of failure returns with the error code. So a 503 error code means that the server is unavailable. This could be because the server crushed or because the IIS is configure for small amount of connections.
If no requests fail, increase the stress factor and do so until reaching capacity.
