Performance bottleneck identification in Nginx - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Identify the output of the NGINX status command

You run the command curl http://localhost/nginx_status on a server with NGINX configured to expose its status. What output do you expect to see?

A

Active connections: 5
server accepts handled requests
 100 100 200
Reading: 1 Writing: 2 Waiting: 2

B

Active connections: 0
server accepts handled requests
 0 0 0
Reading: 0 Writing: 0 Waiting: 0

C Error 404: Not Found

D Syntax error in configuration file

💡 Hint

The NGINX status page shows active connections and request counts.

The NGINX status module outputs the number of active connections, total accepted connections, handled connections, total requests, and the current reading, writing, and waiting connections.

🧠 Conceptual

intermediate

Understanding NGINX worker_processes impact

If your NGINX server has 1 CPU core and you set worker_processes 4; in the configuration, what is the likely effect on performance?

A NGINX will efficiently use all CPU cores and improve performance

B NGINX will automatically reduce worker_processes to 1

C NGINX will refuse to start due to invalid worker_processes setting

D NGINX will create 4 worker processes but only one CPU core is available, causing context switching overhead

💡 Hint

More worker processes than CPU cores can cause overhead.

Setting more worker processes than CPU cores causes unnecessary context switching, which can reduce performance instead of improving it.

❓ Troubleshoot

advanced

Diagnosing slow response times in NGINX

You notice slow response times on your NGINX server. Which of the following is the most likely cause related to NGINX configuration?

A Setting <code>client_max_body_size</code> too high causing slow uploads

B High <code>keepalive_timeout</code> causing connections to close too quickly

C Too low <code>worker_connections</code> limit causing connection queueing

D Using <code>gzip off;</code> which compresses responses unnecessarily

💡 Hint

Connection limits can cause delays when many clients connect.

If worker_connections is too low, NGINX cannot handle many simultaneous connections, causing delays as connections wait.

✅ Best Practice

advanced

Optimizing NGINX for high traffic

Which NGINX configuration change best helps improve performance under high traffic load?

A Enable <code>sendfile on;</code> to reduce disk I/O overhead

B Disable caching to always serve fresh content

C Set <code>worker_processes 1;</code> to avoid process overhead

D Increase <code>client_body_timeout</code> to 300 seconds

💡 Hint

Reducing disk I/O helps serve files faster.

sendfile on; allows NGINX to send files directly from disk to network, reducing CPU usage and improving throughput.

🔀 Workflow

expert

Sequence to identify NGINX performance bottleneck

Arrange the steps in the correct order to identify a performance bottleneck in an NGINX server.

A 1,2,3,4

B 1,3,2,4

C 3,1,2,4

D 2,1,4,3

💡 Hint

Start with NGINX metrics, then system resources, then logs, then config changes.

First check NGINX status to see connection load, then system resources to find hardware limits, then logs for errors, finally tune config.

Practice

1. What is the primary purpose of enabling the stub_status module in nginx?

easy

A. To monitor active connections and request statistics

B. To enable SSL encryption for secure connections

C. To cache static files for faster delivery

D. To compress HTTP responses automatically

Solution

1. Step 1: Understand the stub_status module

   The stub_status module provides a simple way to get real-time statistics about nginx such as active connections and request counts.

2. Step 2: Identify its monitoring role

   It does not handle SSL, caching, or compression but focuses on performance metrics.

3. Final Answer:

   To monitor active connections and request statistics -> Option A

4. Quick Check:

   stub_status = monitor connections and requests [OK]

Hint: stub_status shows live connection and request stats [OK]

Common Mistakes:

• Confusing stub_status with SSL or caching modules
• Thinking it compresses responses
• Assuming it improves performance directly

2. Which of the following nginx configuration snippets correctly enables the stub_status page at /nginx_status?

easy

A. location /nginx_status { stub_status on; allow 127.0.0.1; deny all; }

B. location /nginx_status { stub_status; allow 127.0.0.1; deny all; }

C. location /nginx_status { stub_status on; allow all; }

D. location /nginx_status { status_stub on; allow 127.0.0.1; deny all; }

Solution

1. Step 1: Recall correct stub_status syntax

   The directive to enable stub_status is simply stub_status; without 'on'.

2. Step 2: Check access control correctness

   Allowing 127.0.0.1 and denying others is correct for security.

3. Final Answer:

   location /nginx_status { stub_status; allow 127.0.0.1; deny all; } -> Option B

4. Quick Check:

   stub_status directive has no 'on' [OK]

Hint: stub_status directive has no 'on' keyword [OK]

Common Mistakes:

• Adding 'on' after stub_status
• Using wrong directive name like status_stub
• Allowing all IPs without restriction

3. Given this nginx log excerpt showing many slow requests, which metric indicates a potential bottleneck?

medium

A. High number of 200 status codes

B. Low bytes_sent values

C. Frequent GET requests

D. High request_time values in access logs

Solution

1. Step 1: Understand request_time meaning

   The request_time shows how long nginx took to process a request; high values mean slow responses.

2. Step 2: Analyze other metrics

   Low bytes_sent or many 200 codes do not indicate slowness; frequent GETs are normal traffic.

3. Final Answer:

   High request_time values in access logs -> Option D

4. Quick Check:

   High request_time = slow requests [OK]

Hint: Look for high request_time to spot slow requests [OK]

Common Mistakes:

• Confusing status codes with performance
• Assuming bytes_sent relates to speed
• Ignoring request_time metric

4. You added the stub_status location but get a 404 error when accessing /nginx_status. What is the most likely cause?

medium

A. The location block syntax is incorrect with extra semicolons

B. The server block is missing the listen directive

C. The stub_status module is not compiled or enabled in nginx

D. The allow directive is missing

Solution

1. Step 1: Check module availability

   If stub_status is not compiled into nginx, the location will not work and return 404.

2. Step 2: Verify other config parts

   Incorrect syntax or missing listen usually cause config errors, not 404. Missing allow causes access denied, not 404.

3. Final Answer:

   The stub_status module is not compiled or enabled in nginx -> Option C

4. Quick Check:

   Missing stub_status module = 404 error [OK]

Hint: 404 on stub_status means module missing or disabled [OK]

Common Mistakes:

• Assuming syntax errors cause 404
• Confusing 404 with access denied errors
• Ignoring module compilation status

5. You want to identify if nginx worker processes are a bottleneck under high load. Which combined approach helps you best diagnose this?

hard

A. Check stub_status active connections and use top to monitor worker CPU usage

B. Only check nginx error logs for worker crashes

C. Increase worker_processes blindly without monitoring

D. Disable access logs to reduce disk usage

Solution

1. Step 1: Use stub_status for connection metrics

   stub_status shows active connections and requests, indicating load on workers.

2. Step 2: Monitor worker CPU usage with system tools

   Using top or similar tools shows if workers are maxing CPU, a sign of bottleneck.

3. Step 3: Combine metrics for diagnosis

   Both metrics together reveal if workers are overloaded or if other issues exist.

4. Final Answer:

   Check stub_status active connections and use top to monitor worker CPU usage -> Option A

5. Quick Check:

   Combine stub_status + CPU monitoring = diagnose bottleneck [OK]

Hint: Combine stub_status and CPU tools to find worker bottlenecks [OK]

Common Mistakes:

• Ignoring CPU usage of workers
• Changing config without data
• Relying only on logs or disabling logs