A transaction goal is the least acceptable time for all the responses in a transaction to come back. If the actual response time in one of the test iterations exceeds the goal, then the Missed the Goal counter is incremented. After the test is complete, the percentage of the page and transaction requests that missed the goal is reported in the Missed Goal % column in the Page Details and Transaction Details section, respectively. Also, Goal and Missed Goal curves will be plotted on the graphs in the Transaction Result tab.
To set or change the page goal use the following information: 1. Default goal
Note: When you set a default goal, it affects not only transactions but also pages. |  |
2. Individual page goal. To override the page default goal value, change the Goal(s) property in the property grid. It is recommended to select the goal relevant to your application's quality of service requirements. |  |
Required performance
A transaction's required time is the expected amount of time in which all the responses in a transaction should come back. The required performance time should be faster than the goal time. If the actual response time in one of the test iterations exceeds the required performance time, then the Missed requirement counter is incremented in the Transaction performance counter. To set the required time in seconds, set the Required performance (s) property. The value should be lower than the Goal (s) property.
Missed goal and Missed required performance
If the transaction time is greater than the Goal and Required performance, then only the Missed goal counter will be incremented. The Missed requirement counter will not be affected.
Overview
Content Tools
