Connection pooling to upstream in Nginx - Time & Space Complexity

Time Complexity: Connection pooling to upstream

O(n)

Understanding Time Complexity

We want to understand how the time to handle requests changes when using connection pooling in nginx.

Specifically, how does reusing connections affect the work nginx does as requests increase?

Scenario Under Consideration

Analyze the time complexity of the following nginx configuration snippet.

upstream backend {
    server backend1.example.com;
    server backend2.example.com;
    keepalive 32;
}

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

This config sets up connection pooling with 32 keepalive connections to upstream servers.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Handling each incoming request by reusing or opening connections to upstream servers.
• How many times: Once per request, but connection reuse reduces repeated connection setup overhead.

How Execution Grows With Input

As the number of requests grows, nginx reuses existing connections up to the keepalive limit, reducing repeated setup work.

Input Size (n)	Approx. Operations
10	About 10 request handlings, few new connections
100	100 request handlings, many reuse existing connections
1000	1000 request handlings, most reuse connections, few new setups

Pattern observation: The work per request stays mostly steady because connections are reused, not reopened each time.

Final Time Complexity

Time Complexity: O(n)

This means the total work grows linearly with the number of requests, but connection reuse keeps each request efficient.

Common Mistake

[X] Wrong: "Connection pooling makes handling requests constant time regardless of request count."

[OK] Correct: Each request still needs processing, so total work grows with requests, but pooling reduces repeated connection setup time.

Interview Connect

Understanding how connection pooling affects request handling time shows you can reason about real server efficiency and resource use.

Self-Check

"What if the keepalive value was set to 1 instead of 32? How would the time complexity change?"

Practice

1. What is the main purpose of using keepalive in an upstream block in nginx?

easy

A. To limit the number of client connections to nginx

B. To close all connections immediately after each request

C. To reuse open connections to backend servers and improve response speed

D. To enable caching of static files on the server

Solution

1. Step 1: Understand the role of keepalive in upstream

   The keepalive directive in the upstream block tells nginx to keep a number of connections open to backend servers for reuse.

2. Step 2: Identify the benefit of connection reuse

   Reusing connections avoids the overhead of opening new connections for each request, improving speed and reducing latency.

3. Final Answer:

   To reuse open connections to backend servers and improve response speed -> Option C

4. Quick Check:

   Connection pooling = reuse connections = To reuse open connections to backend servers and improve response speed [OK]

Hint: Remember: keepalive means keep connections open for reuse [OK]

Common Mistakes:

• Thinking keepalive limits client connections
• Confusing keepalive with caching
• Assuming keepalive closes connections immediately

2. Which of the following is the correct syntax to enable connection pooling with 32 keepalive connections in an nginx upstream block?

easy

A. upstream backend { keepalive 32; server backend1.example.com; }

B. upstream backend { keepalive_connections 32; server backend1.example.com; }

C. upstream backend { keepalive=32; server backend1.example.com; }

D. upstream backend { keepalive 32 servers; server backend1.example.com; }

Solution

1. Step 1: Recall the correct directive syntax

   The correct directive to set connection pooling count is keepalive followed by the number, ending with a semicolon.

2. Step 2: Check each option's syntax

   upstream backend { keepalive 32; server backend1.example.com; } uses keepalive 32; which is correct. Options A, B, and C use incorrect directive names or syntax.

3. Final Answer:

   upstream backend { keepalive 32; server backend1.example.com; } -> Option A

4. Quick Check:

   Correct syntax = keepalive 32; = upstream backend { keepalive 32; server backend1.example.com; } [OK]

Hint: Use 'keepalive' followed by number and semicolon inside upstream [OK]

Common Mistakes:

• Using incorrect directive names like keepalive_connections
• Adding extra words after number
• Using equal sign instead of space

3. Given this nginx configuration snippet, what will be the effect on connection reuse?

upstream backend {
    server backend1.example.com;
    keepalive 16;
}

server {
    location / {
        proxy_pass http://backend;
        proxy_http_version 1.1;
        proxy_set_header Connection "";
    }
}

medium

A. Connections will be closed immediately after each request

B. Connections will not be reused because proxy_http_version is 1.1

C. The configuration will cause a syntax error and fail to start nginx

D. Connections to backend will be reused up to 16 times, improving performance

Solution

1. Step 1: Analyze upstream keepalive setting

   The keepalive 16; directive allows nginx to keep up to 16 idle connections open to the backend for reuse.

2. Step 2: Check proxy settings for connection reuse

   Setting proxy_http_version 1.1; and proxy_set_header Connection ""; enables connection reuse by preventing the 'Connection: close' header.

3. Final Answer:

   Connections to backend will be reused up to 16 times, improving performance -> Option D

4. Quick Check:

   keepalive + proxy_http_version 1.1 + empty Connection header = reuse [OK]

Hint: Use HTTP/1.1 and clear Connection header to enable reuse [OK]

Common Mistakes:

• Assuming HTTP/1.1 disables reuse
• Not clearing Connection header disables pooling
• Confusing keepalive with client connections

4. You configured connection pooling with keepalive 10; in your upstream block, but nginx is still opening new connections for every request. What is the most likely cause?

medium

A. You forgot to set proxy_http_version 1.1; and clear the Connection header

B. The keepalive directive only works with HTTP/2

C. You need to increase keepalive to at least 100

D. The backend server does not support keepalive connections

Solution

1. Step 1: Check proxy settings required for connection reuse

   For connection pooling to work, nginx must use HTTP/1.1 and clear the Connection header to avoid closing connections.

2. Step 2: Identify common misconfiguration

   If proxy_http_version 1.1; and proxy_set_header Connection ""; are missing, nginx will close connections after each request despite keepalive.

3. Final Answer:

   You forgot to set proxy_http_version 1.1; and clear the Connection header -> Option A

4. Quick Check:

   Missing proxy_http_version 1.1 + Connection header clear = no reuse [OK]

Hint: Always set proxy_http_version 1.1 and clear Connection header [OK]

Common Mistakes:

• Believing keepalive works without proxy_http_version 1.1
• Thinking backend server must be changed first
• Assuming keepalive number is too low

5. You want to optimize nginx to reuse connections to multiple backend servers with different keepalive limits. Which configuration correctly sets 20 keepalive connections for backend1 and 10 for backend2?

hard

A. upstream backend { server backend1.example.com; keepalive 20; server backend2.example.com; keepalive 10; }

B. upstream backend1 { server backend1.example.com; keepalive 20; } upstream backend2 { server backend2.example.com; keepalive 10; }

C. upstream backend { server backend1.example.com keepalive=20; server backend2.example.com keepalive=10; }

D. upstream backend { server backend1.example.com; server backend2.example.com; keepalive 30; }

Solution

1. Step 1: Understand keepalive scope

   The keepalive directive applies per upstream block, not per server inside it.

2. Step 2: Check options for setting different keepalive values

   upstream backend1 { server backend1.example.com; keepalive 20; } upstream backend2 { server backend2.example.com; keepalive 10; } defines two separate upstream blocks, each with its own keepalive setting, which is correct. Options B, C, and D try to set different keepalive values inside one upstream block, which is invalid.

3. Final Answer:

   upstream backend1 { server backend1.example.com; keepalive 20; } upstream backend2 { server backend2.example.com; keepalive 10; } -> Option B

4. Quick Check:

   Separate upstream blocks for different keepalive values = upstream backend1 { server backend1.example.com; keepalive 20; } upstream backend2 { server backend2.example.com; keepalive 10; } [OK]

Hint: Use separate upstream blocks to set different keepalive values [OK]

Common Mistakes:

• Trying to set keepalive per server inside one upstream
• Using invalid syntax with equal signs
• Setting one keepalive for multiple servers expecting different limits