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.