Before you begin testing from the Cloud
The NeoLoad Cloud Platform can be accessed from the Cloud Console of NeoLoad or from the Tricentis NeoLoad website. Learn more in Connect to the NeoLoad Cloud Platform.
A Cloud Load Generator is a Load Generator available on a machine hosted in the Cloud.
Cloud Load Generators are grouped in sessions.
A Cloud session can contain several Cloud Load Generators in several geographical zones, with a start date and a duration.
Cloud sessions are grouped in workgroups.
A Cloud workgroup contains several sessions, users contacts (administration and technical), and the available, reserved, and used credits/VUHs.
It is made up of users who can use the credits/VUHs to reserve and start Cloud sessions using the NeoLoad Cloud Platform.
Prerequisites
The application to test from the Cloud must be accessible from the Internet.
The NeoLoad Controller must use a connection other than the one used by the application servers to test, to avoid bandwidth issues. The network interface card must be properly sized too. When the Controller is set up on a LAN, the Controller must be able to connect to the Generators on TCP port 443. This connection is made in the Controller-to-Load Generator direction.
The server cloud.saas.neotys.com with the TCP port 443, hosting the NeoLoad Cloud Platform must be accessible from the Controller. The connection to the server hosting the NeoLoad Cloud Platform can be used with a proxy. For more information, see Proxy.
Note: The connection to the Cloud Load Generators can be secured using SSL. For more information, see Use encryption with Cloud-based Load Generators.
VUH Only
1 VUH is 1 Virtual User for an hour.
The VUH Only mode enables you to perform Cloud testing with NeoLoad without having to use a license. You can use only VUH to run a Cloud test with any number of concurrents VUs.
Caution: VUH Only mode can not be used to execute tests designed with RealBrowser.
Connect to the NeoLoad Cloud Platform
The NeoLoad Cloud Platform can be accessed from the Cloud Console of NeoLoad or from the Online Cloud Console.
If you need to:
-
Create and use an on-demand Cloud session.
-
Use an existing or reserved Cloud session.
-
Modify and terminate Cloud sessions.
-
Reboot and terminate Cloud Load Generators.
>> Access the NeoLoad Cloud Platform from the NeoLoad Cloud Console.
If you need to:
-
Reserve a Cloud session.
-
Modify and cancel a reserved Cloud session.
-
Modify and terminate Cloud sessions.
-
Reboot and terminate Cloud Load Generators.
-
Modify the Cloud Load Generators hosts file.
-
Reserve and release IP addresses.
>> Access the NeoLoad Cloud Platform from the Online Cloud Console.
Cloud credits only: Size Cloud Load Generators
Sizing Cloud Load Generators is a crucial step to define the number of User Paths which a Cloud Load Generator can handle. The number of User Paths depends on many aspects:
-
Technologies used in the application to test
-
Complexity of the application to test
-
Network connection capacity
-
Etc.
Starting a ramp-up test of the application with one Cloud Load Generator using an on-demand session in one given geographical region makes it possible to benchmark the Load Generator. NeoLoad monitoring data, and particularly thresholds on the CPU and on the memory of the Load Generator machine, help identify the maximum number of User Paths for the Load Generator.
After identifying the number of User Paths that one Cloud Load Generator can handle and the number of User Paths for the test, it is easy to calculate the number of Cloud Load Generators necessary to run the test.
Note: For more information about on-demand Cloud sessions, see Create an on-demand Cloud session. For more information about ramp-up tests, see Load variation policy. For more information about monitoring thresholds, see Set and configure a counter alert threshold.
Note: For more information about sizing Cloud Load Generators, see Cloud credits only: Size Cloud Load Generators in the Heavy load testing User Guide or contact Neotys Professional Services.
Bandwidth
The bandwidth generally observed is:
-
100 Mbps minimum from the Load Generator to the application to test.
-
100 Mbps minimum from the application to test to the Load Generator.