API
The Gcore Customer Portal is being updated. Screenshots may not show the current version.
Edge Cloud
Edge Cloud
OverviewBillingTerraform
API
Chosen image
Home/Edge Cloud/Networking/Load Balancers/Manage Load Balancer

Manage Load Balancers

The list of created balancers is located inside the project - > Networking - > Load Balancers

There you can:

  • Configure a balancer (the "Overview" option) 
  • Rename a balancer (the "Edit" option) 
  • Delete a balancer

To do it, select the necessary action on the selector on the right from the balancer.

Interface for managing created Load Balancers

Go to your project - > Networking - > Load balancers -> select the Overview option on the selector on the right from the chosen balancer.

In the drop-down window, you can edit existing listeners in the Load Balancer and also add new ones.

Add new Listener

You can edit and delete listeners. Select the appropriate option on the selector on the right from the listener. 

Edit or Delete listeners

In the editor, you can:

  • Change the checking algorithm
_______________.png
  • Parameters of connected Virtual Machines (including verification address, port, and weight)
______________.png
  • Enable and disable Virtual Machines from the load balancing pool
__________________________.png
  • Change the parameters in the Health Check section
Health Check configuration

Load Balancer statuses

Status (UI) Status (API) Value
Healthy Online The balancer is working. All Virtual Machines in the pool accept requests.
Unhealthy Draining A Virtual Machine from the pool does not accept new requests.
Degraded One or more balancer components have the "Error" status.
Error The balancer doesn't work. Virtual machines do not pass check requests. All Virtual Machines in the pool have the "Error" status.

Performance analysis

We’ve tested our Load Balancers to determine the performance of different flavors.

For each flavor, we’ve deployed the client in multithreading mode with 36 concurrent threads and 400 connections over the test duration of 30 seconds.

The results show:

  • Throughput: The number of requests per second (RPS) a Load Balancer can handle under a number of simultaneous users’ requests.

  • Latency: Response times for both HTTP and HTTPS traffic across different Load Balancer flavors.

Flavor HTTP HTTPS
Throughput Latency (ms) Throughput Latency
1 vCPU - 2 GiB 21k 4 20k 20
2 vCPU - 2 GiB 45k 3 34k 12
4 vCPU - 8 GiB 91k 5 51k 8
8 vCPU - 16 GiB 142k 3 117k 4

Was this article helpful?

Not a Gcore user yet?

Discover our offerings, including virtual instances starting from 3.7 euro/mo, bare metal servers, AI Infrastructure, load balancers, Managed Kubernetes, Function as a Service, and Centralized Logging solutions.

Go to the product page
// // Initialize a variable to undefined initially. // var growthBook = undefined; // (function() { // try { // var script = document.createElement('script'); // script.src = "https://cdn.jsdelivr.net/npm/@growthbook/growthbook/dist/bundles/auto.min.js"; // script.setAttribute("data-api-host", "https://cdn.growthbook.io"); // script.setAttribute("data-client-key", "sdk-truekA5wvhMYaqsu"); // document.head.appendChild(script); // script.onload = function() { // console.log("GrowthBook script loaded successfully."); // growthBook = window.GrowthBook; // Assuming GrowthBook attaches itself to window // }; // script.onerror = function() { // console.error("Failed to load the GrowthBook script."); // growthBook = undefined; // Explicitly set to undefined on error // }; // } catch (error) { // console.error("An error occurred while setting up the GrowthBook script:", error); // growthBook = undefined; // } // })(); // // Optional: Push to dataLayer if needed // window.dataLayer = window.dataLayer || []; // window.dataLayer.push({ // 'event': 'scriptLoadStatus', // 'growthBookStatus': growthBook ? "Loaded" : "Failed" // });