What should I measure in my load test?
It is recommended that you record a web surfing session that covers the most used aspects of your web application, and that you execute the same load test several times using a different number of concurrent users for each test run (1, 2, 5, 10, 20, 50, 100 etc.) After performing these tests, you can see a graphical comparison of the measured results called "Load Curves", which will give you an excellent overview of the stability and the maximal capacity of the web application:
You should also have a closer look at the response times per web page, and within each page, at the response time per URL in order to isolate the most time-consuming URLs. If you encounter big differences between the URL response times - which are more or less size independent - you have found valuable candidates for server-side adjustments.
You can obtain a lot of additional information by examining the detail results of each test run. Up to 19 different diagrams and statistics are available. An example is the composition of slowest URL calls; in order to detect memory and resources leaks on the server side, we recommend that you additionally perform an endurance test over several hours by using a moderate number of concurrent users.
Please sign in to leave a comment.