Share this page

# Transactions graphs

This topic describes the graphs that you can use to show analytics for the transactions included in the scenario.

In this topic:

## Transactions graphs overview

During load test scenario execution, Vusers generate data as they perform transactions. Analysis enables you to generate graphs that show the transaction performance and status throughout script execution.

In addition, when working with Network Virtualization, you can view the transaction response times per virtual location.

You can use additional Analysis tools such as merging and crossing results to understand your transaction performance graphs. You can also sort the graph information by transactions and the locations in which they were performed.

## Transaction Breakdown Tree

The Transaction Breakdown Tree displays a tree view of the transactions and sub-transactions in the current session. To access the Transaction Breakdown Tree, right-click in the Average Transaction Response Time or Transaction Performance Summary graph and select Show Transaction Breakdown Tree. From the tree, you can break down transactions and view the results in either the Average Transaction Response Time or Transaction Performance Summary graph.

Note: After you breakdown a transaction, you can return to the original transaction graph by reapplying the global filter (File > Set Global Filter) or by undoing your breakdown actions using Edit > Undo Last Action.

User interface elements are described below (unlabeled elements are shown in angle brackets):

UI Element | Description
--- | ---
<Right-click menu> | Break Down From Highest Level. Displays data for the highest level hierarchical path of a transaction. Break Down <transaction name>. Displays data for the sub-transactions in the Average Transaction Response Time or Transaction Performance Summary graph. Show Only <transaction name>. Displays data only for the selected transaction/sub-transaction. Web Page Diagnostics for <page name>. Displays a breakdown of the web page(s) included in a transaction or sub-transaction in the Web Page Diagnostics graphs. For details, see Web Page Diagnostics graphs.

## Average Transaction Response Time graph

This graph displays the average time taken to perform transactions during each second of the load test scenario run. By default, only transactions that passed are displayed. If you have defined acceptable minimum and maximum transaction performance times, you can use this graph to determine whether the performance of the server is within the acceptable range.

You can also compare this graph to the Running Vusers graph to see how the number of running Vusers affects the transaction performance time. For example, if the Average Transaction Response Time graph shows that performance time gradually improved, you can compare it to the Running Vusers graph to see whether the performance time improved due to a decrease in the Vuser load. For details, see Vuser graphs.

### Breakdown Options

- Transaction Breakdown. To view a breakdown of a transaction, right-click it in the graph and select Show Transaction Breakdown Tree. In the Transaction Breakdown Tree, right-click the transaction you want to break down, and select Break Down <transaction name>. The Average Transaction Response Time graph displays data for the sub-transaction.

  For details, see Transaction Breakdown Tree.

  Web Page Breakdown. To view a breakdown of the web page(s) included in a transaction or sub-transaction, right-click it and select Web Page Diagnostics for <transaction name>.

  For more information, see Web Page Diagnostics graphs.

Axis | Description
--- | ---
X-axis | Elapsed time since the start of the run.
Y-axis | Average response time (in seconds) of each transaction

Tip: This graph is displayed differently for each granularity. The lower the granularity, the more detailed the results. However, it may be useful to view the results with a higher granularity to study the overall Vuser behavior throughout the scenario. For example, using a low granularity, you may see intervals when no transactions were performed. However, by viewing the same graph with a higher granularity, you see the graph for the overall transaction response time. For more information on setting the granularity, see Change the granularity.

## Transactions per Second graph

This graph displays, for each transaction, the number of times it passed, failed, and stopped during each second of a load test scenario run. It helps you determine the actual transaction load on your system at any given moment.

Axis | Description
--- | ---
X-axis | Elapsed time since the start of the run.
Y-axis | Number of transactions performed during each second of the scenario run.

Tip: Compare with the Average Transaction Response Time graph to determine the effect of the number of transactions upon the transaction performance time.

## Total Transactions per Second graph

This graph displays the total number of transactions that passed, the total number of transactions that failed, and the total number of transactions that were stopped, during each second of a load test scenario run. It helps you determine the actual transaction load on your system at any given moment.

Axis | Description
--- | ---
X-axis | Elapsed time since the start of the run.
Y-axis | Total number of transactions performed during the scenario run.

## Total Passed Transactions graph

This graph displays the cumulative sum of passed transactions over the scenario run.

Axis | Description
--- | ---
X-axis | Elapsed time since the start of the run.
Y-axis | The number of transactions that were completed with a Passed status during the scenario run.

## Transaction Performance Summary graph

This graph displays the minimum, maximum and average performance time for all the transactions in the load test scenario.

Breakdown options:

- Transaction Breakdown. To show a breakdown of a transaction in the Transaction Performance Summary graph, right-click the transaction in the graph and select Show Transaction Breakdown Tree. In the Transaction Breakdown Tree, right-click the transaction you want to break down, and select Break Down <transaction name>.

  The Transaction Performance Summary graph displays data for the sub-transactions. For more details, see Transaction Breakdown Tree.

- Web Page Breakdown. To view a breakdown of the web page(s) included in a transaction or sub-transaction, right-click it and select Web Page Diagnostics for <transaction name>. For more, see Web Page Diagnostics.

Axis | Description
--- | ---
X-axis | Name of the transaction.
Y-axis | The response time, rounded off to the nearest second for each transaction.

## Transaction Response Time (Distribution) graph

This graph displays the distribution of the time taken to perform transactions in a load test scenario. It is only displayed as a bar graph. You can compare with Transaction Performance Summary Graph to see how the average performance was calculated. If you have defined acceptable minimum and maximum transaction performance times, you can use this graph to determine whether the performance of the server is within the acceptable range.

For example, you can view this graph to verify that the majority of the transactions had a response time of less than 30 seconds.

Axis | Description
--- | ---
X-axis | Transaction response time (rounded down to the nearest second).
Y-axis | Number of transactions executed during the scenario.

## Transaction Response Time (Percentile) graph

This graph analyzes the percentage of transactions that were performed within a given time range.

Item | Description
--- | ---
Purpose | Helps you determine the percentage of transactions that met the performance criteria defined for your system. In many instances, you need to determine the percent of transactions with an acceptable response time. The maximum response time may be exceptionally long, but if most transactions have acceptable response times, the overall system is suitable for your needs. For example, your graph might show that fewer than 20 percent of the abc transactions had a response time of less than 70 seconds.
X-axis | Percentage of the total number of transactions measured during the load test scenario run.
Y-axis | Maximum transaction response time (in seconds). Note: Analysis approximates the transaction response time for each available percentage of transactions. The y-axis values, therefore, may not be exact.
Tips | Compare with the Average Response Time graph. A high response time for several transactions may raise the overall average. However, if the transactions with a high response time occurred less than five percent of the time, that factor may be insignificant.

## Transaction Response Time (Under Load) graph

This graph is a combination of the Running Vusers and Average Transaction Response Time graphs and indicates transaction times relative to the number of Vusers running at any given point during the load test scenario.

Item | Description
--- | ---
Purpose | Helps you view the general impact of Vuser load on performance time and is most useful when analyzing a scenario with a gradual load.
X-axis | Number of running Vusers
Y-axis | Average response time (in seconds) of each transaction.

## Transaction Response Time by Location graph

This graph shows the average transaction response time for each of the virtual locations with which the transactions were performed. The bars in the graph are color-coded by virtual location – the same color is displayed for all transactions that use the same virtual location.

This graph is used in conjunction with NV (Network Virtualization). Using NV, you set up a scenario that runs Vusers on several virtual locations. It helps you view the general impact of Vuser load on performance time for each virtual location. Then you can determine if there are any network issues with a particular location. For details, see Network Virtualization.

Axis | Description
--- | ---
X-axis | Transactions performed with a specific virtual location.
Y-axis | Average response time (in seconds) for each transaction, per virtual location.

## Transaction Summary Graph

This graph summarizes the number of transactions in the load test scenario that failed, passed, stopped, and ended in error.

The graph shows the number of transactions performed during the run, for each transaction name.

Item | Description
--- | ---
X-axis | Name of the transaction.
Y-axis | Number of transactions performed during the scenario run.

## See also

- Analysis graphs

- Web Page Diagnostics

https://admhelp.microfocus.com Professional Performance Engineering,VuGen 8942
Tips to improve your search results... OpenText™ Professional Performance Engineering Help Center OpenText™ Professional Performance Engineering Help 26.1-26.3 All View Local Help Center View Online Help Center Version: