Engineering Sizing Utility

Virtual Users (VU) & RPS Load Test Calculator

Size your HTTP load tests accurately before execution. Compute required concurrent Virtual Users from target Requests Per Second (RPS), p50/p99 latency, and think time using Little’s Law.

Load Presets:
Little’s Law Parameters
Configure Workload & Latency Profile
Adjust target arrival rate (RPS), median/tail response times, and client think time to compute required Virtual Users.

λ (Arrival rate): How many HTTP requests per second your endpoint must process.

W (Service time): Typical HTTP round-trip latency under normal operating conditions.

Models how many Virtual Users get tied up if your backend slows down to p99 latency.

Z (Think time): Pause between sequential requests per Virtual User (0ms for raw API benchmarks).

Total execution window used to estimate cumulative request volume and plan fit.

Computed Concurrency Profile
Little’s Law Sizing Output
VU = 40 RPS × (150ms + 200ms) / 1000

Steady-State VUs

14

At p50 (150ms)

Recommended VUs

18

+25% headroom buffer

p99 Surge Concurrency:32 VUs
Throughput per Single VU:2.86 req/s
Tail-to-Median Ratio (p99/p50):4×
Total Requests (60s):2,400 reqs
Matching LoadTest Tier
$9 / month

Starter Plan

For solo developers and small projects

  • Up to 50 VUs / 50 RPS
  • Up to 5 min per test run
Run this profile on Starter
The Engineering Formula: Little’s Law for HTTP Load Testing
Why concurrency (VU), arrival rate (RPS), and response time (W) are mathematically locked together.

In queueing theory, Little’s Law (L = λ × W) states that the long-term average number of items in a stationary queueing system (L) equals the long-term average effective arrival rate (λ) multiplied by the average time that an item spends in the system (W).

VU = ceil( Target_RPS × ((ResponseTime_ms + ThinkTime_ms) / 1000) )

When a Virtual User pauses for client think time (Z) between requests, that VU slot remains occupied for W + Z seconds per request cycle. Ignoring response time or think time when picking VU counts leads to either severely under-driving your target API or exhausting worker sockets prematurely.

Quick Reference Lookup Table (0ms Think Time)
Minimum steady-state Virtual Users required to sustain target RPS at different API response times.
Target RPS50 ms API150 ms API300 ms API1,000 ms API
10 RPS1 VU2 VUs3 VUs10 VUs
50 RPS3 VUs8 VUs15 VUs50 VUs
200 RPS10 VUs30 VUs60 VUs200 VUs
1,000 RPS50 VUs150 VUs300 VUs1,000 VUs
Want the full queueing-theory breakdown?Read VU vs. RPS Guide

Frequently Asked Load Sizing Questions

How do you convert Requests Per Second (RPS) to Virtual Users (VUs)?

Using Little’s Law from queueing theory: VU = RPS × ((ResponseTime_ms + ThinkTime_ms) / 1000). For example, if your API target is 100 RPS, median response time is 200 ms, and think time is 0 ms, each Virtual User completes 5 requests per second (1000 / 200), requiring 20 concurrent VUs.

Why should I add a 25% headroom buffer to my calculated Virtual Users?

Steady-state VU math uses median (p50) latency. In real HTTP tests, tail requests (p95 and p99) take significantly longer, tying up active Virtual User threads. Adding a 25% VU buffer prevents your load generator from becoming the bottleneck when latency fluctuates.

How does client think time affect required Virtual Users?

Think time increases the total cycle duration (W + Z) of each Virtual User without generating additional server load during the pause. Adding 800 ms of think time to a 200 ms API call increases cycle time from 0.2s to 1.0s, requiring 5× more concurrent VUs to sustain the same RPS.