Can payload size vary?

Yes in production, but this version uses a single average payload.

Is this enough for final validation?

No. Run real load tests and compare against telemetry.

Load test simulator

Q: Does this include ramp-up?

No. Output is steady-state estimation for the active period.

Simulate expected throughput, total requests and test data volume for a given duration and user behavior profile.

Simulator

Concurrent usersRequests per flowThink time (seconds)Avg response time (ms)Test duration (minutes)Avg payload per request (KB)

Simulation output

Expected RPS

240

Total requests

144,000

Estimated data volume

562.50 MB

Throughput per minute

14,400

This model assumes stable behavior for all virtual users. Real tests include jitter, retries and warmup effects.

What this simulator estimates

It estimates load magnitude and generated traffic volume over a fixed duration using user cycle assumptions.

How to use it

cycle_seconds = think_time + (response_time_ms / 1000)
RPS = (users * requests_per_flow) / cycle_seconds
total_requests = RPS * duration_seconds
volume_kb = total_requests * payload_kb

Use this output to size generators, network budgets and storage projections for observability pipelines.

Example test plan

With 200 users, 3 requests per flow, 2s think time and 500ms response time for 10 minutes, expected RPS is about 240 and total requests around 144,000.

FAQ

Does this include ramp-up?

No. This estimate represents steady-state behavior during the active test period.

Can payload be different per endpoint?

Yes in reality, but this tool uses one average payload for V1 simplicity.

Is this enough for final capacity signoff?

No. It is a planning baseline before running real tests.