Cross-Vuser transactions are transactions that allow you to measure the duration of a process that involves multiple Vusers. For example, you can create a cross-Vuser transaction to determine how long it took the receiving party to get the information that was sent. This transaction type originates from one Vuser and ends at another.
The Vusers who start and end the transaction, form a cross-Vuser pair.
A cross-Vuser transaction is not limited to two Vusers. It also includes broadcasting, in which one Vuser sends a message to many Vusers. In this case, the broadcaster, who begins the transaction, and the receivers, who end the transaction, together form a cross-Vuser group.
For both a cross-Vuser pair and a cross-Vuser group, the transaction is initiated by a single Vuser.
You must define a transaction ID to serve as an identifier for each cross-Vuser pair or group. The ID must be a string that uniquely identifies the pair or group. All Vusers in a pair or group share the same identifier.
It is recommended that you create a standard for the transaction ID . The ID string should indicate whether the cross-Vuser transaction is related to a pair or group.
In the above example, in Transaction1, if the sender is "black", the receiver is "red", and the message is "message1", then a logical ID string could be black_red_message1. In Transaction4, if the sender is "black", then a logical ID string could be black_broadcast.
The following examples illustrate typical scenarios for cross-Vuser transactions:
- The time it took from when one user sent an email to when another user received it.
- The time it took for users to see a message posted on a social network.
Use the following guidelines when creating a script with cross-Vuser transactions:
- Cross-Vuser transactions do not calculate think time, waste time, and so forth—only duration time is recorded.
- Cross-Vuser transaction data is not used by the Controller's transaction monitors.
- LoadRunner cannot detect the status of cross-Vuser transactions.
For details on how to create cross-Vuser transactions, see How to Create a Cross-Vuser Transaction.
After you complete your replay, you can view the results in LoadRunner Analysis, as you would with ordinary transactions.