Workers and Deployment

LoadEng distributes scenarios to traffic-generator units (workers); these units send requests according to task definitions and collect metrics. This page explains worker concepts, setup, and distributed test models.

What is a worker?

Each worker sends HTTP requests to target endpoints based on assigned scenario tasks. You can run multiple worker instances on a single machine or distribute workers across different servers/regions. When a test starts, the system sends scenario data to registered workers; workers generate traffic and report telemetry back to the control plane.

Worker setup

  • Install: Install the worker component on your target server or container. Use the version compatible with your operating system.
  • Configure: Provide API address and, if required, authentication data (token or certificate) via environment variables or config files.
  • Connect: Once started, worker connects to backend and is marked as "ready". When a run starts, the system assigns scenario tasks to available workers.
  • Network: Ensure worker can access both backend services and test targets (URLs). Configure firewall and proxy rules accordingly.

Deployment and scaling

By running workers across multiple geographies or network segments, you can test targets with realistic distributed traffic. For example, for a web application you can simulate concurrent users from Europe and Asia by running workers in each region. You can increase total RPS by adding more workers; scenario concurrency and duration parameters are applied across all active workers together.

TLS, certificate, and security settings are described in LoadEng deployment documentation and environment-specific runbooks.

Important notes

  • At least one worker must be connected and ready; otherwise scenario runs cannot start.
  • Workers should send requests only to targets you define; do not run tests against unauthorized systems.

Next steps

Use Scenarios and Tests to review the scenario lifecycle. Continue with API Reference for API and integration details.