Featured AI Products
Compute
Build, deploy, and scale cloud compute resources
Containers and Images
Safely store and manage containers and backups
Managed Databases
Fully managed resources running popular database engines
Management and Dev Tools
Control infrastructure and gather insights
Networking
Secure and control traffic to apps
Security
Help protect your account and resources with these security features
Storage
Store and access any amount of data reliably in the cloud
Browse all products
AI/ML
CMS
Data and IoT
Developer Tools
Gaming and Media
Hosting
Security and Networking
Startups and SMBs
Web and App Platforms
See all solutions
Community
Documentation
Developer Tools
Get Involved
Utilities and Help
Become a Partner
Marketplace
Pricing

- Community
- DigitalOcean
- Community
- DigitalOcean

Is load balancers decrease bandwidth speed?

Posted on February 28, 2017

I’m planned to use load balancer to my droplets.

But, I’m concern about bandwidth speed.

If I have two droplets with 50Mbps speed (for each droplet). I can serve content to 100 visitors with 1Mbps speed at the same time.

When I’m using Load Balancer (if load balancer is also have same speed 50 Mbps limit) I can serve content to 100 visitors with 500Kbps speed at the same time.

Is it right? Also, Is DigitalOcean set any bandwidth speed limits on load balancer?

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Jonathan Tittle

February 28, 2017

Accepted Answer

@chandranakka

Using a Load Balancer won’t cut download speeds, it simply balances incoming requests and directs them to a server in your configured cluster. If you’re using DigitalOcean’s Load Balancer service, you would choose either Round Robin or Least Connections when setting up the LB, which is what will determine how visitors are directed to the Droplets you’ve attached.

Round Robin configuration means that visitors will be directed to the first available server in the mix. As long as that first server is deemed active, it’ll be the one to serve incoming requests. Should that server go down, Round Robin connects to the next active server that’s available to handle requests.

Least Connections works a little different in that it keeps track of which server has the most activity as well as the least activity. The least active server that’s configured will be the one to receive the next request. For example, if you have 2 Droplets and one has 100 connections while another has 50, the one with 50 will serve the next request and so forth and so on.

You’re not dividing bandwidth or download capabilities by using a LB, you’re simply balancing the load of incoming requests by directing them to multiple servers instead of a single.

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

View all products

Start building today

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.