loadrunner monitoring tools 김범수 [email protected] 한국비지네스써비스 ( 주 )
TRANSCRIPT
Agenda
Definition of problem Using the Transaction Breakdown facility Using the Network Monitor Using the Resource Monitor
Definition of Problem
Transaction timings indicate that a problem exists but does not tell where the problem lies
Transaction Breakdown
Currently available only for 2-tier Oracle Gives a general idea of where the problem lies Breaks transaction into 5 elements
– Network + Client– CPU– I/O– Database locks– Other
Enabling Transaction Breakdown
Install LoadRunner agent on Oracle Server Enable transaction breakdown option in the
controller Run Scenario Analyze results Click transaction breakdown option on the
toolbar
Fix DB Locking Problem
Programmer can modify code to prevent locking
Enable transaction breakdown facility Rerun scenario Analyze results
Network Monitoring Elements
Path delay Segment delay Timeouts Path delay under load Segment delay under load
Enabling Network Monitoring
Not necessary to install LoadRunner Enable Network Monitoring option Run Scenario Analyze results
Fix Network Problem
Make any network changes Rerun scenario View Networking Monitor and Transaction
Breakdown results
Resource Monitor
Monitors machine’s resources during scenario run
Displays these resources in real time NT measurements correspond to those
available from the NT Performance Monitor Unix measurements correspond to those
available from the rstat daemon
Summary
Run a scenario Analyze results If results ok - done If not ok
– Use transaction breakdown to pinpoint problem– Use network & resource monitors to further analyze
the problem– Fix problem– Go back to step one