Worker processes and connections in Nginx - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding worker_processes directive

What is the primary role of the worker_processes directive in the nginx configuration?

A It specifies the timeout duration for worker processes.

B It defines the maximum number of simultaneous connections per worker.

C It sets the number of worker processes to handle client requests.

D It configures the logging level for worker processes.

💡 Hint

Think about how nginx handles multiple requests at the same time.

The worker_processes directive sets how many worker processes nginx will spawn. Each worker handles client requests independently, so increasing this number can improve concurrency.

💻 Command Output

intermediate

Output of nginx status with worker connections

Given the nginx configuration with worker_processes 2; and worker_connections 1024;, what is the maximum number of simultaneous client connections nginx can handle?

A 2048

B 1024

C 512

D 4096

💡 Hint

Multiply the number of worker processes by worker connections.

The maximum simultaneous connections is worker_processes multiplied by worker_connections. Here, 2 * 1024 = 2048.

❓ Configuration

advanced

Correct nginx configuration for high concurrency

Which nginx configuration snippet correctly sets 4 worker processes and allows each to handle 2048 connections?

A

worker_processes 4;
worker_connections 2048;

B

worker_processes 2048;
worker_connections 4;

C

worker_processes 4;
worker_connections 1024;

D

worker_processes auto;
worker_connections 2048;

💡 Hint

Remember the directives control processes and connections separately.

Setting worker_processes 4; and worker_connections 2048; means 4 workers each can handle 2048 connections, maximizing concurrency.

❓ Troubleshoot

advanced

Troubleshooting connection limits in nginx

If nginx is configured with worker_processes 2; and worker_connections 1024; but clients experience connection refusals under high load, which is the most likely cause?

A The <code>worker_processes</code> value is too high.

B The server has too much RAM.

C The <code>worker_connections</code> value is ignored by nginx.

D The OS limit on open files is too low, restricting connections.

💡 Hint

Nginx depends on OS limits for file descriptors.

Even if nginx is configured for many connections, the OS limits on open files (file descriptors) can restrict actual connections, causing refusals.

✅ Best Practice

expert

Optimal use of worker_processes with CPU cores

What is the best practice for setting worker_processes in nginx on a multi-core server to maximize performance?

A Set <code>worker_processes</code> to double the number of CPU cores.

B Set <code>worker_processes</code> equal to the number of CPU cores.

C Set <code>worker_processes</code> to the number of active network connections.

D Set <code>worker_processes</code> to 1 regardless of cores.

💡 Hint

Think about how nginx uses CPU resources.

Setting worker_processes equal to the number of CPU cores allows nginx to efficiently use all cores without overhead from too many processes.