# Load Testing — RPM Solutions

Load testing validates that a system meets its service-level objectives under
realistic production load. It is a pass/fail validation exercise against
explicit, pre-agreed criteria.

## Approach

Workload model built from production analytics (transaction mix, arrival rates,
think times, data variety). Typical profile: ramp to target over 15–30 min,
sustain plateau ≥ 60 min so caches warm and pools reach steady state.

Example pass criteria: p95 ≤ 500 ms, p99 ≤ 1,200 ms, error rate < 0.1%,
no resource above 75% sustained utilisation.

## Measured

Latency percentiles (never averages alone), throughput (requests and business
transactions per second), error rates by type, server-side saturation: CPU,
memory/GC, connection and thread pools, database wait events, queue depths.

## Typical findings

Undersized connection pools, N+1 query patterns, cache misconfiguration,
chatty service-to-service calls, database lock contention under concurrency.