Load testing

Measure your own staging system inside a defined test window.

Agree on the measurement window

The staging owner approves a small batch of report-generation jobs and defines a stop threshold. Use fixed synthetic inputs, monitor the origin's queue and record how many reports finish inside the agreed window. Keep this traffic within the authorized environment.

How to run the review

Agree request ceilings, a monitoring owner and a stop condition. Separate queueing at the client from load at the application.

Network selection

Compare the characteristics of dedicated proxies with the test's geographic and session requirements. Check the planned region in the coverage directory.

Session setup

Use fixed dedicated egress agreed with the staging owner. Keep rotation disabled so monitoring can attribute traffic to the scheduled test and enforce its agreed limits.

Frequently asked questions

Which person can stop the test?

Name an on-call owner before the window opens and confirm they can stop the workload immediately when the agreed ceiling or error threshold is reached.

How do we distinguish application saturation from a slow test runner?

Compare client queue time with origin receipt and completion timestamps. A growing client queue before the origin sees the work points to a different bottleneck.