How to load test in full Cloud

For tests fully performed and managed in the Cloud, it may be useful to tune the scenarios in the on-premise Controller to optimize the testing environment, before setting the NeoLoad Cloud Controller and the Cloud Load Generators, as described in Select and configure the NeoLoad Cloud Controller and Select the Cloud Load Generators.

• To load test in full Cloud

1. Open your scenario in the on-premise NeoLoad Controller.
2. Check the design of your scenario:
   • For the requests, ensure the validations, if any, are really necessary. Keep them only for the key pages whenever you can.
   • For the variables values, ensure the distribution policies are not Controller-based whenever you can.
   • Ensure the validations and the variable extractions on bulky inputs, if any, are really necessary and optimize them.
   • For the variables extractors:
     • Ensure the XPath expressions, if any, are really necessary.
     • Ensure the regular expressions with quantifier backtracks are really necessary.
     • Limit the number of small Virtual Users, if any, or redesign them.
   • For the Virtual Users, ensure the JavaScript actions, if any, are really necessary and reduce their number whenever you can.

   See Configure the scenarios.

3. Check the configuration of your project from the on-premise NeoLoad Controller:
   • Configure a limited duration for your test.
   • Limit the number of monitoring metrics or keep the default selected ones.
   • In Edit > Preferences > Project Settings > Runtime parameters, disable Store previous response data on error.
   • In the Runtime section, select the scenario, click Advanced, then disable Display Virtual User status during the test.
4. Set enough time to reserve your NeoLoad Cloud Controller.

   See Reserve and configure the NeoLoad Cloud Controller.

5. Configure the infrastructure to optimize the performance of the heavy load testing.

   See Configure the network.

6. When the reserved NeoLoad Cloud Controller is available:
   • Set up the Windows firewall, as described in Set up the Windows firewall.
   • Activate your license or transfer your local license.
   • Upload your project.
   • If you have modified or added some keys in the local controller.properties file, duplicate these keys only in the controller.properties file of the NeoLoad Cloud Controller.
   • When using a local Monitoring Agent, check that the NeoLoad Cloud Controller can access it.
7. Only if you are paying with Cloud credits: Size your Cloud Load Generators with an on-demand Cloud session:
   • Create an on-demand Cloud session with one Load Generator.
   • Ensure the Controller accesses the Neotys Cloud Platform and the Cloud Load Generator (both of them on port 443).
   • Start a ramp-up test in no debug mode.
   • Identify the significant breaking point in the CPU, memory, throughput or hit rate metrics.
   • Identify the number of Virtual Users at that breaking point.

   See Cloud credits only: Size Cloud Load Generators.

8. If you need to use the same IP addresses for the whole test campaign, reserve IP addresses.

   See Reserve IP addresses.

9. Set enough time to reserve your Cloud session and get your Cloud Load Generators.

   See Reserve the Cloud Load Generators.

10. When your reserved Cloud Load Generators session is available, start the test:
    • Do not use the debug mode.
    • Run a short preliminary load test to make sure that:
      • the Cloud Load Generators have access to the tested application,
      • the license is properly installed,
      • the monitoring counters are set up as expected.
    • Warm up the application with one or two lower tests.
    • Start your heavy load test.

    See Start the test.

11. Terminate the test.
12. Download useful content from the NeoLoad Cloud Controller:
    • NeoLoad project
    • Reports
    • Log files
13. Terminate the Cloud session.
14. If necessary, release the NeoLoad license.
15. Read the test results.

    See Read and retrieve results.

Home