Transaction time for Action1_Transaction is not equal to the sum of all transactions in Action1
How does LoadRunner determine the total transaction time for Action1_Transaction? When taking the sum of all the transactions in Action1 section and comparing it with Action1_Transaction, the numbers do not match.
With automatic transactions, LoadRunner internally calls a Start_Transaction function at the beginning of Action1 to start a timer, then calls a End_Transaction at the end of Action1 section to stop the timer. The total timing is reported as Action1_transaction in the Analysis report.
Most of the time, the Action1_transaction reported is slightly different from the sum of all the user-defined transactions. The extra timing may include:
- Think times added to Action1_transaction which are not included in any of the user-defined transactions
- Some extra steps included in the Action1_transaction that do not fall under any of the user-defined transactions
- Action1_transaction includes the time it takes to call and process a transaction step (i.e., start or end which does not get included into the user-defined transaction)