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?"