Updated May 14, 2026
Private load generation
Generate load from a private location when the target API, staging system, or partner path should not be exposed publicly.
What this workflow should produce
- Traffic originates from an approved network boundary.
- The run still appears in the shared Maxoperf results workflow.
- Teams can compare private and managed-location runs without changing tools.
Use case
Private load generation is for systems that should not be made public just so a test can reach them. It keeps traffic near the target while preserving a shared run and result workflow.
How Maxoperf supports it
Maxoperf lets teams attach private runner locations and choose them during test planning. The run record still includes the scenario, load profile, logs, metrics, and result context.
A practical rollout
Begin with a low-pressure test window and a clearly authorized target. Confirm network access, result collection, and runner health before increasing load.
FAQ
When should private load generation be used?
Use it when the target is private, regulated, latency-sensitive, or intentionally unreachable from public managed locations.