Need help with StresStimulus? Start here.
How to interpret graphs
|
Unregistered User Posts: 509
11/6/2017
|
I am unclear how to read the graphical results. Our product is a single page application. Therefore, the slowest pages don’t carry the same meaning like in the server aspx architecture. Here is one of the examples.
The average statistics / text are clearke to gain a solid understanding of the charts to be able to explain in meetings and more importantly improve the response times / weak areas of our product.
|
|
|
0
link
|
|
George @StresStimulus Administrator Posts: 555
11/6/2017
|
StresStimulus creates performance metrics for requests, pages and transactions. You are correct that in your case, performance metrics for pages is not relevant. You should disable it. To do so, when you record a test case, uncheck the box “group requests into pages”, as shown on step 3 here
If you already recorded with the page breakdown and do not wish re-record, delete pages in the test case tree. This will remove irrelevant metrics on your reports.
Regarding graph metrics, below is an example how to read response time on KPI graph - the green line. Because Range = 10, the 93% value on the graph represents 9.3 seconds. This is your maximum response time of a single request. To determine which requests cause the slowness, you have to look at the test result -> detail view -> request details, as described here Since the graphs are interactive, you can also zoom in in the graph for more detailed analysis of the problem areas.
StresStimulus also can monitor your server infrastructure and report metrics of Windows performance counters as described here You can select meaningful metrics out of hundreds available Windows performance counters. You would be able than correlate slow response time with extreme value of a specific metrics of a Web server, ASP.NET or SQL Server.
|
|
|
0
link
|
Copyright © 2024 Stimulus Technology