The document outlines the key performance testing requirements when using LoadRunner. It discusses factors that impact throughput like hardware specifications, software processing overhead, and degree of parallelism. It also defines different types of performance tests including load testing to determine maximum load, stress testing under deprived resources, soak testing under prolonged load, and scalability testing to determine if an application can scale. Finally, it lists requirements for scripts, parametrization, correlations, scenarios, think times, and monitoring tools for capacity planning when using LoadRunner for performance testing.

1. ***Performance Testing Requirements
* Throughput: It indicates
(a). number of transactions per second an application can handle
(b). amount of transactions produced over time during a test
Throughput depends on different factors:
(1). specifications of the host computer
(CPU Speed, RAM Size & Allocation, Network Speed, Disk RW Speed, IOPS/ IOs)
(2). processing overhead in the software
(RAM Utilization by the Software, Response Time)
(3). Degree of parallelism both hardware and software
(Monolithic OS, Hybrid OS, CPU Architecture, Parallel Processing, Connection Pool, DB Choice
and Architecture of RDBMS/ DB Server, Normalization, Mirroring, Load Balancing, Software
Architecture, Hardware Architecture including that of the Motherboard, NIC Cards)
(4). Types of transactions being processed (Messaging Queues, Threading, RT (Real Time
Transaction System), Hyper Threading, Batch Processing, CPU Cache)
* Response Time
(Depends upon response in milliseconds, NIC Design and CPU, Router Capacity (capacity to handle
so many packets per second, MTU size))
* Network Latency
( % Packet Drops, Network Bandwidth)
* CPU Utilization
* % Disk Busy (Depends on Disk IOPS/ Ios)
* % Free Memory/ % RAM Utilization
(Depends on RAM Speed and MTR (MB Maximum Transfer Rate))
* Caching/ Paging/ Swapping
* Threshold Limit
* Memory Leakage
(Depends on Ramp Up, Ramp Down, Garbage Collection, Memory Heap/ Heap Size)

2. * Performance Testing
To Determine Behavior of the System under given Load Conditions
* Load Testing
To Determine the Maximum Subjected Load that a System can handle at a given point of time.
Depends Upon Number of Users Handled at a Given point Time
* Stress Testing
To Determine the Behavior of the System under deprived resource conditions
* Soak Testing
To Determine the Behavior of the System under prolonged subjected Load Conditions
* Scalability Testing
To Determine whether an application can be scaled up in terms of:=
increased resource usage or by increased number of users
* Endurance Testing
To Determine the Behavior of the System under endured or subjected load for given increasing/
varying Load Conditions/ duration
*** Performance Testing using LoadRunner Requirements
* Business Case Stories/ Real World Situations
* Scripts to be captured in VUGen or Coded in VUGen
* Parametrization for Unique Data Constraints
* Correlation for Dynamic Data being submitted in POST or Submit Transactions
* Goal Oriented Scenario
* Manual Scenario
* % Wait Time or Response Wait Time or Sleep Time
* Think Time
* Rendezvous Points
* Retry Intervals
* Transaction Steps
* Sampling Period
* Ramp Up Duration
* Ramp Down Duration
* % Hits Per Second
* Unique Data
* Sequential Data
* Random Data
* Response Time
* Standard Logging
* Extended Logging

3. ***Profiling or Monitoring Tools for Capacity Planning
Wily Sitescope
Wily Introscope
Shunra WAN Emulator
TeamQuest
Solarwinds Librato Dashboard
PerfMon
Windbg
IDA PRO
HIEW
SysInternals
NETSTAT
IOSTAT
TaskManager
ps
ping
iptrace
tracert
top
sysadm
memstat