What are the hardware resources allocated to my account for load generators?
Every paid LoadFocus load testing plan includes a set number of load generators and a fixed hardware size per generator. The generators are AWS machines that create the virtual users (VUs) for your cloud, JMeter and k6 tests. The Pricing page lists both under Load Generators and Hardware configuration.
Load generators and hardware per plan
Section titled “Load generators and hardware per plan”| Plan | Load generators | Hardware per machine |
|---|---|---|
| Free | Not listed | Not listed |
| Starter | 1 machine | 2 vCPUs, 6 GB RAM |
| Basic | 2 machines | 2 vCPUs, 6 GB RAM |
| Essential | 5 machines | 4 vCPUs, 10 GB RAM |
| Pro | 10 machines | 8 vCPUs, 20 GB RAM |
| Enterprise | 20 machines | 16 vCPUs, 32 GB RAM |
Virtual users, test length, runs and locations are separate limits of each plan, listed in Plans and limits together with the Free plan and trial rules.
What this means for your test
Section titled “What this means for your test”A generator has a fixed amount of CPU and memory, so the number of virtual users it can drive depends on how heavy your script is. A plan with larger machines and more of them can run heavier scripts and more virtual users at once.
Where the generators run
Section titled “Where the generators run”You choose the AWS regions for each test in the test configuration, see Geographical test location. How many locations a single test can use depends on your plan.
Every request in a test comes from LoadFocus generators in the regions you pick, so a firewall, WAF or bot protection in front of the target sees traffic from cloud servers. Allow the LoadFocus IP ranges before you test such a host. Otherwise the results measure the protection instead of your application (see Errors by type).
When a generator is the limit
Section titled “When a generator is the limit”A generator that runs near its CPU limit slows your measurements down. If any generator peaks at or above 80% CPU during a run, the results show a warning that names it, and for JMeter runs the Engine Health tab has the CPU, memory, network and disk of each generator over the run. See Load generator saturation for how to recognise it and how to fix the test, for example by spreading the same users over more locations.