FUNCTIONAL POINT OF VIEW
From functional point of view we can assume that:
Thread = Single User
Query = Action/Click that user performs on ARAS UI
So if we configure 100 threads that uses 500 queries it will
mean that we will simulate work of 100 users that clicks on
actions in ARAS Web UI 500 times.
Those users can perform actions in parallel so it may be that some actions will be send to ARAS at same time - in this configuration.
Additionally the load test tool can be installed on any number of servers or client machines. That permits the simulation geographically distributed usage scenarios.
Example: four servers; one each in Frankfurt, Virginia,
London, Beijing; additionally four client machines. Each
machine runs 200 threads. The total test simulates then 8 *
200 = 1600 users