background image
<< Path Delay Under Load Graph | Determining the Problem Segment >>
<< Path Delay Under Load Graph | Determining the Problem Segment >>

Determining Bottlenecks through Network Monitoring

Monitoring Network Monitoring
LoadRunner Controller User's Guide (Windows)
Chapter 20, page 325
Determining Bottlenecks through Network Monitoring
You can use the Network Monitor to:
determine whether the network is the bottleneck
determine the
bad
segment, if you already know that the Network is the
bottleneck.
Verifying the Network as a Bottleneck
You can use the Network Monitor graphs to determine if the network is a bottleneck
using the Timeouts and Path Delay Under Load graphs.
The Timeout Count graph indicates loss of data and multiple retries. The Network
Monitor checks network performance by sending packets of information over the
network. If a packet does not return within a specified period, a timeout signal is
generated. All of the timeouts that occurred during a scenario are displayed in the
Timeouts graph. Multiple timeouts show that the network is overloaded. For
information on setting the timeout period, see
Configuring the Network Monitor
on page 327.
The Path Delay Under Load graph shows the path delay relative to the number of
running Vusers. If the delay increases (in a higher range than the increase of
transaction time) with the number of running Vusers, the network is overloaded.
However, if the network delay remains constant, but the transaction time increases,
the problem lies in a different component of the transaction.