March 7, 2013
The reports available in LoadStorm supplement the graphs by providing additional detail beyond the key performance indicators visible in the graphs. All reports are accessible under the Analyze tab by clicking on the Details button next to the load test you wish to view. There are essentially 5 different views of the load test results: Summary Report – presents cumulative results for the complete load test. Requests by Elapsed Time – request/response specifics listed sequentially in one-minute increments. Requests by Error Code – lists any requests that trigger an error. Requests by Response Time – shows the slowest resources in […]
Read more March 7, 2013
The Summary Report is on the same page with the graphs and shows performance metrics for the entire load test. The counts are also split out by HTML pages versus ancillary resources such as images, stylesheets, XML, and script files. This Summary Report shows: Response time (average) – shows the average time it takes to get a response per request. Errors – shows the total number of errors. Requests – shows the total number of requests. RPS (average) – shows the average number of requests sent per second. RPS (peak) – shows the largest number of requests sent in per […]
Read more March 7, 2013
Below are two screenshots of the two graphs that appear for each load test. In the actual application, the actual value of the metrics will appear when you mouse over one of the lines (shown). Volume Graph The first one shows the volume of traffic hitting your server. It shows three lines representing these metrics: Concurrent Users Requests per Second Throughput Requests per Second RPS is the measurement of how many requests are being sent to the target server. It includes requests for HTML pages, CSS stylesheets, XML documents, JavaScript libraries, images and Flash/multimedia files. RPS will be affected by […]
Read more March 7, 2013
This screen shot shows how the Requests by Elapsed Time report breaks down all of the load test requests into one minute intervals. By clicking on one of the intervals, you get the raw data for every request and response that occurred in that minute of the load test. The following is what a single interval report looks like – only a few of the rows are shown.
Read more March 7, 2013
This report shows all responses that contained a status code that indicates a problem with fulfilling the request. Assuming that your web application has been functionally tested for bugs and the bugs have been fixed before load testing begins, errors are a key way to see when your app has performance problems. Here is a small sample of a report that shows the error code, what requested resource caused the error, and how many times this resource received the error during this load test: Web servers return errors to tell the user/browser that it did not properly handle the request, […]
Read more March 7, 2013
This reports shows which resources were the slowest performers during this load test. The columns in the report are: Resource Number of Requests for this Resource Average Size Average Response Time Maximum Response Time The rows are sorted by Average Response Time, so this report quickly shows you which resource requests take the longest time to fulfill. You will notice that it is common for some resources to have a faster average response, but have one or two requests that took much longer. These outliers may be important to your application tuning, or they may be insignificant anomalies. That’s why […]
Read more March 7, 2013
If a request gets a response returned with a status code that indicates a failure or a response doesn’t return in 35 seconds (timeout), then the vuser continues to move to the next step in its scenario. For instance, if a JavaScript file fails to download during step 3: That error will be logged in LoadStorm for reporting That request will be terminated All other requests for step 3 will be attempted as usual The vuser will begin step 4 as defined in the scenario If any particular resource times out within a step, some of the step processing may […]