Estimated virtual users
135
VU Calculator for JMeter and k6
Use this VU Calculator to estimate how many virtual users you need for JMeter and k6 load tests based on target RPS, response time, think time and requests per flow.
Users estimation
Result
Cycle time (s)
2.25
How to calculate VUs for JMeter
In JMeter, the estimated VU value maps directly to Thread Group - Number of Threads (users). Start with this baseline, then tune ramp-up and pacing based on observed p95 latency and error rate during the test.
Next step: use the Ramp-up Calculator to convert users into users/second.
How to calculate VUs for k6
In k6, use the estimated VU count as a starting point for `vus` or staged scenarios. Validate the target RPS with real response-time behavior, then adjust VUs to keep latency and failure rate inside acceptable thresholds.
If your load is bursty, combine this with the Load Test Simulator.
How it works
This VU calculator applies a practical load-testing model: virtual users are derived from target RPS and cycle time (response time + think time).
Formula
cycle_seconds = think_time + response_time_ms / 1000
virtual_users = (target_rps * cycle_seconds) / requests_per_flowUse p95 response time for conservative planning. Add safety margin for retries, distributed generator overhead, and temporary spikes.
Example
If target is 250 RPS, response time is 300ms, think time is 2s and requests per flow is 2, estimated VUs are 287.5 (round up to 288+).
FAQ
What is a VU in JMeter?
A VU in JMeter is usually one thread/user in a Thread Group. It represents one concurrent virtual user executing your test flow.
How many VUs do I need in k6?
Use this VU Calculator estimate as a baseline, then calibrate in k6 by checking achieved RPS, p95 latency and error rate.
VU vs RPS: what changes with think time?
Higher think time increases cycle duration, so you need more VUs to maintain the same target RPS.