User can learn more fundamental information from test list page and can run tests such as stop and delete (when test status is running, it can only be stopped). The ball is marked as test status and it will refresh every 5 seconds. By hovering the mouse over it, you can view test status tips.
Test configuration is a critical aspect of running a test. This sets the test duration, Agent, processes, number of threads etc in the test before running the test. Of course there are also more specific configuration items to satisfy a range of users.
|Agent||The number of Agents should be used.|
|Vuser per agent||The number of virtual users in each agent , which is multiplied by process count and thread count.
You can configure them in greater detail by clicking the + button.
In the nGrinder stress test, all agents will have multiple processes and threads to simulate concurrent users.
|Processes (Hidden)||The number of worker processes the agent should start.|
|Threads (Hidden)||The number of worker threads that each worker processes.|
|Script||Test script to be used.|
|Target Host||For every test, we should set the target host; it should be same as the host you access in your test script. nGrinder controller will start the monitoring task on the target host when a test begins to run. Then, you can check the performance chart in the detailed test report.
We implemented customized DNS resolving for the target host. This means we can just input a domain address that is used in intervals, and input the actual IP. This will be useful for some http servers, which have no DNS domain, and need to use domain address for access.
|Duration||Specify how the test will be executed.|
|Run Count||Specify how many test runs will be executed.|
|Ignore Sample Count||Specify How many samples will be ignored during TPS collecting.|
If you check the Ramp-up check box, you can specify a gradual initialization of the process.
|Ramp-Up||This means increasing the number of processes in every interval.|
|Initial Sleep Time|
|Initial Processes||This property sets the initial number of worker processes to start.|
|Processes Every||This property sets the interval in milliseconds at which the agent starts new worker processes.|
Please remember this is process ramp-up!!.. So you must have enough process count to increase the count gradually. If you set up, 1 agent, 10 processes and 2 threads, the count of vuser will be increased like 2, 4, 6, 8.... if you set the 1 in Ramp-Up. If you set 2 agents, it wil be 4, 8, 12, 16.
The count of processes should be less than 10. Too many processes requires agent memory much. So you can not configure ramp-up very smoothly. If you need to have very smooth ramp-up, please consider the thread ramp-up.
Currently, there will initially be a maximum of 10 tests running simultaneously by default, and one user can only run one test at the same time. All the agents will be assigned automatically to run some test. If there are not enough agents to run one test, that test will be delayed for several minutes, and then stopped as an error.
When a user creates a test, the user can choose just to save the test or prepare it to run. If it is prepared to run, the test (including its configuration) cannot be modified or deleted. But the user can clone this test and create a new test with the same configuration.
The test can also be scheduled to run later, rather than starting immediately.
At the bottom right, you can download the log file for each agent. Using this file, you can identify script execution problems.