Introduction

It is a kind of rare case, but sometimes you will not get good enough performance by just one Agent Loader.

This page shows how to use more than one.

We suggest to always start with just one Loader. Use more when you find one is not sufficient.

Code example

Here is how you set running your actions on one Loader:

LoadClient loader = new LoadClient( ADDRESS_LOADER_1 );

And here is how you set running your actions on more than one Loader:

LoadClient loader = new LoadClient( ADDRESS_LOADER_1, ADDRESS_LOADER_2 );

This is all you have to change in your test code.

ATS will automatically split as evenly as possible the number of threads based on the number of loaders.

The Application Under Test will not make a difference if you interact with it by using one or more Loaders.

You will need to have more than one Agent and you will need to deploy your Agent components containing your actions at more than one Agent.

Unfortunately, we can't give you the exact answer, but we can share some thoughts with you.

The Loader itself can easily start hundreds or even thousands of threads as the ATS Agent(Loader) is a normal Java application.

Basically you can think in two directions regarding the number of Loaders and number of running threads(users):

The work your actions do. Some action needs more power, some less. ATS does not know what your particular action will do - it will just run it.
Limitations of your version of Java, your Operating system, and Hardware.

A bit of general advice is to start with one Loader. If you find it not sufficient, then either use it on better hardware or just add another one.