Why load balancing distributes traffic in Nginx - Performance Analysis

Time Complexity: Why load balancing distributes traffic

O(n)

Understanding Time Complexity

We want to understand how the work done by nginx changes when it distributes traffic across servers.

Specifically, how does the number of requests affect the processing time in load balancing?

Scenario Under Consideration

Analyze the time complexity of the following nginx load balancing configuration.

upstream backend {
    server backend1.example.com;
    server backend2.example.com;
    server backend3.example.com;
}

server {
    listen 80;
    location / {
        proxy_pass http://backend;
    }
}
    

This code sets up nginx to distribute incoming requests evenly across three backend servers.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Routing each incoming request to one of the backend servers.
• How many times: Once per request, repeated for every request nginx receives.

How Execution Grows With Input

As the number of requests increases, nginx processes each request by selecting a backend server.

Input Size (n)	Approx. Operations
10	10 routing decisions
100	100 routing decisions
1000	1000 routing decisions

Pattern observation: The number of routing operations grows directly with the number of requests.

Final Time Complexity

Time Complexity: O(n)

This means the work nginx does grows in a straight line with the number of requests it handles.

Common Mistake

[X] Wrong: "Load balancing makes nginx handle requests faster regardless of how many requests come in."

[OK] Correct: Load balancing spreads requests but nginx still processes each request once, so total work grows with requests.

Interview Connect

Understanding how nginx handles many requests helps you explain real-world server behavior clearly and confidently.

Self-Check

"What if we added more backend servers? How would the time complexity of request handling change?"

Practice

1. Why does Nginx use load balancing to distribute traffic across multiple servers?

easy

A. To increase the size of the server's hard drive

B. To prevent any single server from becoming overloaded and improve response time

C. To reduce the number of servers needed

D. To make the website design look better

Solution

1. Step 1: Understand the purpose of load balancing

   Load balancing spreads incoming requests across multiple servers to avoid overloading one server.

2. Step 2: Recognize the benefit of spreading traffic

   By distributing traffic, servers handle requests faster and the service stays stable.

3. Final Answer:

   To prevent any single server from becoming overloaded and improve response time -> Option B

4. Quick Check:

   Load balancing improves speed and stability [OK]

Hint: Load balancing shares work to keep servers fast and stable [OK]

Common Mistakes:

• Thinking load balancing increases server storage
• Believing it reduces the number of servers needed
• Confusing load balancing with website design

2. Which of the following is the correct syntax to define a load balancing group in Nginx?

easy

A. server_group backend { 192.168.1.10; 192.168.1.11; }

B. loadbalance backend { server 192.168.1.10; server 192.168.1.11; }

C. upstream backend { server 192.168.1.10; server 192.168.1.11; }

D. proxy_pass backend { server 192.168.1.10; server 192.168.1.11; }

Solution

1. Step 1: Identify Nginx load balancing syntax

   Nginx uses the upstream block to define a group of servers for load balancing.

2. Step 2: Check the correct block and server entries

   The correct syntax is upstream backend { server IP; server IP; } to list servers.

3. Final Answer:

   upstream backend { server 192.168.1.10; server 192.168.1.11; } -> Option C

4. Quick Check:

   Use upstream for server groups [OK]

Hint: Remember: 'upstream' defines server groups in Nginx [OK]

Common Mistakes:

• Using 'loadbalance' instead of 'upstream'
• Writing 'server_group' which is invalid
• Misusing 'proxy_pass' inside server group

3. Given this Nginx config snippet, what happens when a client sends a request?

upstream backend {
  server 192.168.1.10;
  server 192.168.1.11;
}
server {
  location / {
    proxy_pass http://backend;
  }
}

medium

A. The request is distributed between 192.168.1.10 and 192.168.1.11

B. The request is sent to only 192.168.1.10 every time

C. The request is blocked because of missing proxy settings

D. The request is sent to 192.168.1.11 only

Solution

1. Step 1: Understand the upstream block

   The upstream backend defines two servers to share traffic.

2. Step 2: Analyze proxy_pass usage

   The proxy_pass http://backend; sends requests to the upstream group, distributing load.

3. Final Answer:

   The request is distributed between 192.168.1.10 and 192.168.1.11 -> Option A

4. Quick Check:

   Requests split across servers [OK]

Hint: proxy_pass to upstream sends requests to all servers [OK]

Common Mistakes:

• Thinking requests always go to first server
• Assuming proxy_pass blocks requests without extra config
• Believing requests go to only one fixed server

4. You configured Nginx load balancing but all traffic goes to one server only. What is the likely cause?

medium

A. The upstream block has only one server listed

B. The load balancing method is set to 'ip_hash'

C. The servers are offline

D. The proxy_pass URL does not match the upstream name

Solution

1. Step 1: Check upstream and proxy_pass names

   If proxy_pass points to a different name than the upstream block, load balancing won't work.

2. Step 2: Understand traffic routing

   Requests will not be distributed if proxy_pass does not reference the correct upstream group.

3. Final Answer:

   The proxy_pass URL does not match the upstream name -> Option D

4. Quick Check:

   proxy_pass must match upstream name [OK]

Hint: proxy_pass name must match upstream block name exactly [OK]

Common Mistakes:

• Ignoring mismatch between proxy_pass and upstream name
• Assuming offline servers cause all traffic to one server
• Confusing load balancing methods with traffic distribution issues

5. You want to ensure Nginx distributes traffic evenly but also keeps a user's requests on the same server. Which load balancing method should you use?

hard

A. ip_hash

B. least_conn

C. random

D. round_robin

Solution

1. Step 1: Understand load balancing methods

   round_robin distributes evenly but does not keep user sessions on one server.

2. Step 2: Identify method that keeps user on same server

   ip_hash uses client IP to send requests to the same server, maintaining session consistency.

3. Final Answer:

   ip_hash -> Option A

4. Quick Check:

   ip_hash keeps user on same server [OK]

Hint: Use ip_hash to stick users to one server [OK]

Common Mistakes:

• Choosing round_robin for session persistence
• Confusing least_conn with user stickiness
• Thinking random method keeps sessions consistent