Distributed Architecture

Run PureLoad in stand-alone on one machine or in a distributed load test environment with multiple load servers.

Distributed Architecture

PureLoad can be setup in a distributed architecture, where load can be generated from a single machine or distributed onto multiple machines. The distributed architecture of the product allows load generation, simulating millions of virtual users. This architecture can be designed using a combination of several Windows, Linux and/or MAC hosts.

A typical distributed architecture would look like this:

The Console

The PureLoad Console (running the GUI) is the central point of control when managing a load session and executing a load test. It is used to assign workers and worker threads, design scenarios and evaluate the output from a load session.

Naming & Taskspace

The Naming server is used to control other servers and is the central point of control in the runtime environment.
The taskspace server is where the defined scenarios are stored and controlled during a load test session. It is also responsible for initializing parameters generated by parameter generators.


Workers are the actual machines generating the load towards the tested system. These are set-up and managed through the Console.


PureLoad also works in a stand alone mode and then run on a single machine. In the stand-alone mode the Console, the Naming and Taskspace server, and the workers will all run simultaneously on one machine supporting smaller load scenarios.

Virtualized Distributed Environments

To support virtualized deployments vPureLoad has been developed as a maintainable and supportable PureLoad virtualization base, covering the whole software stack (operating system, hypervisor, optimizations and PureLoad). For more info see our vPureLoad Solution page.

Continue to Next Chapter - Scenarios View