Performance bottleneck identification in Nginx - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a performance bottleneck in the context of nginx?

A performance bottleneck is a point in the nginx server or its environment that limits the overall speed or capacity, causing slower response times or reduced throughput.

beginner

Which nginx directive helps monitor active connections to identify bottlenecks?

The stub_status directive provides a simple status page showing active connections, accepted connections, handled connections, and requests, useful for spotting bottlenecks.

intermediate

How can slow client connections cause performance bottlenecks in nginx?

Slow clients hold connections open longer, consuming worker resources and reducing nginx's ability to serve new requests quickly, leading to bottlenecks.

intermediate

What role does the worker_processes directive play in performance bottleneck identification?

Setting worker_processes to match CPU cores helps nginx handle more simultaneous connections efficiently, reducing bottlenecks caused by CPU limits.

beginner

Name a tool commonly used alongside nginx to analyze performance bottlenecks.

Tools like htop, top, and netstat help monitor system resources and network connections to identify bottlenecks affecting nginx.

Which nginx module provides a simple status page to check active connections?

A http_ssl_module

B stub_status_module

C gzip

D proxy_pass

The stub_status module shows active connections and request stats, useful for spotting bottlenecks.

What does increasing worker_processes in nginx configuration usually help with?

A Handling more simultaneous connections

B Reducing disk usage

C Improving SSL encryption speed

D Compressing responses

More worker processes allow nginx to handle more connections concurrently, reducing CPU bottlenecks.

Which of these is NOT a common cause of nginx performance bottlenecks?

A High CPU usage

B Insufficient worker processes

C Using gzip compression

D Slow client connections

Using gzip compression generally improves performance by reducing response size, not causing bottlenecks.

Which tool can you use to monitor CPU and memory usage affecting nginx performance?

A git

B curl

C vim

D htop

htop shows real-time CPU and memory usage, helping identify resource bottlenecks.

What does a high number of 'writing' connections in nginx status indicate?

A Many clients are slow to receive data

B Nginx is restarting

C Disk space is full

D SSL handshake failed

Writing connections mean clients are slow to receive data, which can cause bottlenecks.

Explain how you would use nginx's stub_status module to identify performance bottlenecks.

Think about what the status page shows and how it relates to server load.

Describe common causes of performance bottlenecks in nginx and how to address them.

Consider both nginx settings and system resource factors.

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