My Cloud Load Generator is frozen, what can I do?

The NeoLoad interface allows you to interact with your Load Generators.

  1. Choose the Runtime section, and the Scenarios tab.
  2. In the Load Generators area, click on the Open the Cloud Management Console button.
  3. Select your Cloud session and your Load Generator.
  4. Click on the Reboot button.

For more information, see Test from the Cloud.

Best solutions

NL-NETWORK-01 errors


Typically NL-NETWORK-01 errors occur when your server fails to respond with the expected result that NeoLoad awaits. The following article serves as a best practice guide for you to attempt to resolve on your own. Since there are several reasons for NL-NETWORK-01 errors, we need to focus on examples like:

Using one or a combination of the solutions provided will help you troubleshoot in hopes that you achieve a quick resolution.

Typical Error Messages

" No route to host: connect"

" Connection reset"

So how can you tell if it's a server or a network issue?

The Best Solutions for you to Consider

  1. Increase the number of load generators for your test: Your test could be exceeding the total number of requests that are possible on a given load generator, so increasing to more load generators will spread the load out more evenly.
  2. Run your test using less virtual users: To identify if your servers are genuinely overloaded, try using a smaller number of virtual users to rule out other issues.
  3. Disable antivirus or your computer's firewall: Run the test after disabling the antivirus/firewall in an attempt to get to the root cause of the error(s). To use a Controller and Load Generator either side of a firewall, it is necessary to open a TCP port on the LG's interface (in the Controller-to-Load Generator direction). For more details, click here.
  4. Change NeoLoad's settings: There are some settings that could help with containing these types of errors that we have seen from our customers.
  5. Tune your Load Generator(s): The NeoLoad Load Generators code is optimized for multi-core and multi-processor environments. For example, with a machine with four cores, it is vital to make sure the rest of the machine is adequately dimensioned in order to use the available CPU capacity properly. Regarding memory, 1 Gb per core is a good compromise; in this case, 4 Gb of allocated memory is ideal. It is necessary to add to that a 64-bit operating system (to be able to use more than 1.5 Gb of memory), which makes 6 Gb of physical memory. In the case of network adapters, a good compromise is to have one adapter for two cores. For more details, click here.