Understand TPS in AIQ Performance Testing

Recommended guidance

Transactions per second (TPS) measures how many completed business transactions or requests are processed during a test window. In AIQ performance testing, define TPS carefully before comparing runs because different teams may count transactions, pages, API calls, or user journeys differently.

What to define

• The exact transaction boundary: request, step, business action, or full journey.
• The measurement window used for average, peak, and sustained TPS.
• Whether failed, timed-out, retried, or partially completed transactions are included.
• The user load, ramp-up, pacing, test data, and environment used for the result.
• The related metrics: response time, error rate, throughput, CPU, memory, and network utilization.

How to use TPS

1. Validate the script and data at low load before treating TPS as meaningful.
2. Compare TPS only between runs with the same scenario, load model, and environment.
3. Watch for increasing error rate or response time when TPS rises.
4. Document whether the reported TPS is target, achieved, peak, or sustained.

Last updated: October 6, 2026