Why tuning handles high traffic in Nginx - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is tuning worker_processes important in NGINX for high traffic?

NGINX uses worker_processes to handle connections. What happens if this value is set too low on a multi-core server?

A NGINX will automatically increase worker_processes to match CPU cores.

B NGINX will crash immediately due to resource exhaustion.

C NGINX will use more memory but handle requests faster.

D NGINX will not fully use all CPU cores, causing slower request handling.

💡 Hint

Think about how CPU cores and worker processes relate.

Setting worker_processes too low means fewer processes handle requests, so CPU cores remain underused, slowing down traffic handling.

💻 Command Output

intermediate

What is the output of checking active connections in NGINX?

After enabling the stub_status module, you run curl http://localhost/nginx_status. What output shows active connections?

Nginx

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

A server accepts handled requests

B Reading: 1 Writing: 2 Waiting: 2

C Active connections: 5

D 100 100 200

💡 Hint

Look for the line that directly states active connections.

The line starting with 'Active connections:' shows the current number of active connections handled by NGINX.

❓ Configuration

advanced

Which NGINX configuration snippet correctly increases the maximum number of open file descriptors?

To handle high traffic, you want to increase the limit of open files NGINX can use. Which snippet correctly sets this in the nginx.conf?

A worker_connections 65535;

B worker_rlimit_nofile 65535;

C max_open_files 65535;

D open_files_limit 65535;

💡 Hint

Look for the directive that controls file descriptor limits.

worker_rlimit_nofile sets the maximum number of open files for worker processes, which is essential for handling many connections.

❓ Troubleshoot

advanced

Why does NGINX return 'too many open files' error under high traffic?

NGINX logs show 'too many open files' errors during peak traffic. What is the most likely cause?

A The <code>worker_rlimit_nofile</code> or system file descriptor limit is too low.

B NGINX worker_processes is set higher than CPU cores.

C The <code>keepalive_timeout</code> is set too high.

D The <code>client_max_body_size</code> is too small.

💡 Hint

Think about system limits on open files.

NGINX needs enough file descriptors to handle connections. If limits are too low, it cannot open new files/sockets, causing errors.

🔀 Workflow

expert

Order the steps to tune NGINX for handling high traffic efficiently

Arrange these steps in the correct order to tune NGINX for high traffic:

A 1,2,3,4

B 3,1,2,4

C 1,3,2,4

D 2,1,3,4

💡 Hint

Think about setting base limits before increasing connections and applying changes last.

First set worker_processes, then increase worker_connections, adjust file limits, and finally reload NGINX to apply.