LoadView is a cloud-based load testing tool. Cloud-based load testing provides you with a powerful infrastructure to run load tests from a fully-managed cloud environment. Unlike on-premises testing from your own machines, using a cloud environment saves your time and money on building and managing your own infrastructure. Moreover, LoadView uses real browsers and instantiates user load from more than 20 geographical locations, giving you the most realistic conditions to what your users can expect.

Cloud load testing is a must for public web applications or websites. However, what if a target web application is not available from the public Internet? With the Public Proxy and On-site Agent options, LoadView still is a viable alternative to internal load testing. In this article, we will give you an overview of the load testing approaches that are available for both public web applications and web apps behind the firewall.

Load Testing Option  Target Type Do I Need to Configure the Firewall for Load Test? Network Proxy 
Public Cloud Available from the public Internet No Not in Use
Public Proxy Behind the firewall Whitelist the dedicated LoadView IPs. Public Proxy
On-site Agent Behind the firewall No On-site Agent

Public Cloud-based Load Testing with LoadView

When to use

Use to load test web services, websites, or web applications that are available from the public Internet.

How to start

  • Create a LoadView account.
  • Make sure your firewall is opened for inbound traffic and the target web resource is available from the public Internet.
  • Set up and run the load test.

How it works

  • To emulate virtual users, we launch Load Injector Servers (LI) with randomly allocated IPs using Amazon Web Services (AWS) and Azure Cloud Services.
  • The list of IPs used for the test can be downloaded right after the test starts.

Public Proxy for Cloud Testing Behind the Firewall

When to use

Use to load test web resources behind the firewall and when your firewall can be opened for inbound connections from the specific IPs.

How to start

  • Create a LoadView account.
  • Whitelist LoadView Public Proxy IPs for each selected geo-zone in your firewall settings.
  • Set up the load test: set Public for the Network Proxy option in the Load Test Scenario.

How it works

  • To emulate virtual users, we launch Load Injector Servers (LI) with static IPs.
  • All traffic is sent from the static IPs to your network. The list of public proxy IPs can be found here.

On-site Load Testing with LoadView On-site Agent

When to use

Use to load test web resources that are not publicly available and when you don’t want to open your firewall for any incoming traffic.

How to start

  • Create a LoadView account.
  • Install LoadView On-site Agent application on a dedicated Windows Server inside the same network as the target web resource.
  • Enable outbound traffic to Dotcom-Monitor services.
  • Set up the load test: set the Network Proxy option to On-site Agent in the Load Test Scenario.

How it works

  • Once the On-site Agent has been configured, it uses port 443 to send outgoing requests to Dotcom-Monitor Service to check if any load tests were started for the corresponding target website and requests the load test configuration.
  • Once the test configuration with Load Injector IPs has been received by the On-site Agent, it initiates multiple connections to these IPs from within the local network.
  • Load Injectors use the same connections to send load testing traffic to the On-site Agent.
  • All load testing traffic to the target will be sent via the On-site Agent from the company network.
  • Load testing results will be sent to LoadView and available in your LoadView account.