Expires directive in Nginx - Time & Space Complexity

Time Complexity: Expires directive

O(n)

Understanding Time Complexity

We want to understand how the Expires directive affects nginx's work as it handles many requests.

Specifically, how does the time nginx spends change when more files have expiration times set?

Scenario Under Consideration

Analyze the time complexity of the following nginx configuration snippet.

location /images/ {
    expires 30d;
    add_header Cache-Control "public";
}

This snippet sets a 30-day expiration for files in the /images/ folder, telling browsers to cache them.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: nginx checks the request URL against the location and applies the expires rule.
• How many times: This check happens once per request, no loops over multiple files.

How Execution Grows With Input

Each request triggers a simple check and header addition, regardless of how many files have expires set.

Input Size (n)	Approx. Operations
10 requests	10 checks and header additions
100 requests	100 checks and header additions
1000 requests	1000 checks and header additions

Pattern observation: The work grows directly with the number of requests, not with the number of files configured.

Final Time Complexity

Time Complexity: O(n)

This means nginx spends time proportional to the number of requests, doing a quick check each time.

Common Mistake

[X] Wrong: "Setting expires on many files makes nginx slower for each request."

[OK] Correct: nginx applies expires per request without scanning all files, so the number of files with expires does not slow down each request.

Interview Connect

Understanding how configuration directives affect request handling time helps you explain performance impacts clearly and confidently.

Self-Check

"What if we added multiple expires directives in nested locations? How would that affect the time complexity per request?"