background image
<< Using WinRunner and VXRunner to Create GUI Vuser Scripts | Measuring Server Performance: Transactions >>
<< Using WinRunner and VXRunner to Create GUI Vuser Scripts | Measuring Server Performance: Transactions >>

The Virtual User Development Environment

GUI Vuser Scripts Developing GUI Vuser Scripts
Creating Vuser Scripts
Chapter 26, page 445
Measuring Server Performance: Transactions
You define
transactions
to measure the performance of the server. Each
transaction measures the time it takes for the server to respond to specified Vuser
requests. These requests can be simple tasks such as waiting for a response for a
single query, or complex tasks, such as submitting several queries and generating
a report.
To measure a transaction, you insert LoadRunner functions to mark the beginning
and end of a task. Within a script, you can mark an unlimited number of
transactions for analysis, each with a different name, and starting and ending in
different places.
During scenario execution, LoadRunner measures the time that it takes to perform
each transaction. For instance, you could define a transaction to measure the time
it takes for a bank server to process a Vuser's request to view the balance of an
account. After the scenario run, you analyze the server's performance per
transaction using LoadRunner's graphs and reports.
Once you have defined a transaction, you use it to measure how the server
performs under different loads. For example, you can measure how the server
performs under the load of a single user, a hundred users, or a thousand users.
While the scenario runs, LoadRunner accumulates performance data for the
transactions. Later, you use this information to generate performance analysis
reports and graphs.
transactions