Configuring the concurrency and the Load Scenario

In BlazeMeter, the load is generated by a distributed JMeter architecture. A JMeter console is used to control the test and you need to choose the number of JMeter Engine(s) that will participate in the test.

Each JMeter Engine will simulate the number of threads/virtual users specified in the script you provide. For example: 20 engines and a script with 100 threads will generate the traffic of 2,000 simultaneous users.

We recommend running up to 1,000 threads/virtual users per one JMeter Engine if you are using a HTTP/S protocol.

The number of users that can be simulated depends on a number of factors. For more information, please read: The Three Most Common Issues When Running JMeter Scripts and How to Solve Them.

The number of supported threads depends on your script intensity and available resources. The more intense your script – the fewer threads a single JMeter Engine can support.

For example, a test with 10 JMeterEngine(s), each running 300 threads, simulates a total of 3,000 users.

In general, we recommend not to go over the following limits:

  • Up to 600 hits per second per JMeter Engine
  • Up to 300Mbps per JMeter Engine

***We strongly recommend running a high number of JMeterEngine(s) using a headless configuration. A headless configuration is much more efficient in terms of resource allocation.***

Threads Per Server - Auto-Configuration

If you will check the 'USERS' option, the system will automatically allocate the number of engines, and set the amount of threads per engine*.

*This is a very general allocation. Each scenario has it's own ideal amount of threads per engine.

Threads Per Server - Manual Configuration

If you uncheck the 'USERS' option, the system will not automatically allocate the number of engines, and you'll have to set the amount of engines and threads per engine manually.

This option enables users to gain full control over their testing resources.

Threads Per Server - Not Overriding Jmeter's Configuration

You can check the 'Engines' option and uncheck 'Threads' & 'Users' in order for BlazeMeter to NOT override these thread group parameters (as seen below).

Have more questions? Submit a request


Please sign in to leave a comment.