Root directive in Nginx - Time & Space Complexity

Time Complexity: Root directive

O(n)

Understanding Time Complexity

We want to understand how the time it takes for nginx to serve files changes as the number of requests grows.

Specifically, how the root directive affects this process.

Scenario Under Consideration

Analyze the time complexity of the following nginx configuration snippet.

server {
    listen 80;
    server_name example.com;

    root /var/www/html;

    location / {
        try_files $uri $uri/ =404;
    }
}

This snippet sets the root directory for serving files and tries to find requested files or folders.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Checking if the requested file or directory exists on disk.
• How many times: Once per incoming request.

How Execution Grows With Input

Each new request causes nginx to check the file system once to find the file under the root path.

Input Size (n)	Approx. Operations
10	10 file system checks
100	100 file system checks
1000	1000 file system checks

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

Final Time Complexity

Time Complexity: O(n)

This means the time to serve files grows linearly with the number of requests.

Common Mistake

[X] Wrong: "The root directive causes nginx to scan the entire directory for every request."

[OK] Correct: nginx directly checks the requested file path under the root, not the whole directory, so it does one quick check per request.

Interview Connect

Understanding how nginx handles file requests helps you explain server efficiency and resource use clearly, a useful skill in many tech roles.

Self-Check

"What if we changed try_files to check multiple fallback files? How would the time complexity change?"