Health checks in Nginx - Time & Space Complexity

Time Complexity: Health checks

O(n)

Understanding Time Complexity

We want to understand how the time needed for nginx health checks changes as the number of backend servers grows.

Specifically, how does nginx handle checking many servers and how does that affect performance?

Scenario Under Consideration

Analyze the time complexity of the following nginx health check configuration snippet.

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

    health_check;
}

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

This snippet configures nginx to check the health of three backend servers regularly before sending traffic to them.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: nginx sends health check requests to each backend server.
• How many times: Once per server per health check interval.

How Execution Grows With Input

As the number of backend servers increases, nginx performs one health check per server each interval.

Input Size (n)	Approx. Operations
3	3 health checks
10	10 health checks
100	100 health checks

Pattern observation: The number of health check operations grows directly with the number of servers.

Final Time Complexity

Time Complexity: O(n)

This means the time spent on health checks grows linearly as you add more backend servers.

Common Mistake

[X] Wrong: "Health checks happen once for all servers together, so adding servers doesn't increase work."

[OK] Correct: nginx checks each server individually, so more servers mean more checks and more time.

Interview Connect

Understanding how health checks scale helps you design systems that stay reliable as they grow. This skill shows you can think about system behavior beyond just writing configs.

Self-Check

"What if nginx performed health checks in parallel instead of sequentially? How would the time complexity change?"