Test results in Visual Studio can be confusing, so I am going to try to do a very quick breakdown to help explain some of the results values you can see in Visual Studio for load tests. The below table applies to TEST TIME, TRANSACTION TIME, PAGE TIME, etc.
The column for “Performance Counter Data” refers to any values captured that are used for building graphs. Detailed Data refers to the data that is used to display values in the Tables.
|Topic||“Performance Counter Data”||“Detailed Data”|
|How is it collected?||Agents report to the controller a value (I think it is the average time) for all iterations of a test during the previous sampled interval.||Agents store the data on the agent machine for every iteration during the test.|
|When is it collected?||Every Sampling Interval||Only after the test is completed|
|Where is it stored?||In the LoadTestPerformanceSample table||In the LoadTest*Detail table(s)|
|Where do the min/max/avg values come from?||These are computed against the sampled values in the LoadTestPerformanceCounterSample table||These are calculated AFTER the results from ALL agents get stored in the DB. There are stored procs that populate the LoadTest*SummaryData tables with the values.|
|Where is the data displayed in Visual Studio?||Only in the GRAPH tab||Only in the TABLE tab (this is why there is a slim chance you will see a MAX and Average value differ between a table and a graph. One is statistical info and the other is actual info)|
|What is the difference between “statistics only” and “All individual details” in the run settings?||Nothing||All details get loaded to the database REGARDLESS of the setting. The difference is whether the results get deleted from the details tables after the statistics are calculated.
The Prc_UpdateSummaryData3 S.P. is executed regardless, but the second argument passed in is a BIT that is used for determining whether to clear the tables after computing the results.
|How is the percentile Data calculated?||Percentile data is calculated as part of the data population in the Prc_UpdateSummaryData3 execution. The total list of timing details is sorted, then the bottom value of the TOP XX% is set for the XX percent. Here’s an example for 90% percent:
I have 100 values stored for the response time for transactionX, the list is sorted slowest to fastest. Then I take the Top 10 % (SQL Query), which gives me the slowest 10% of the responses (so in this case I get 10 values back). Then I get the smallest value of these (meaning the fastest of the ten percent) and make that value my 90% value.
In other words, for 100 sorted values, my 90% is the timing for the 91st slowest transaction. If I have 1000 entries, then it would be the 901st value.