Worker processes and connections in Nginx - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the role of worker_processes in nginx?

It sets the number of worker processes that nginx will start. Each worker handles client requests independently, improving performance by using multiple CPU cores.

beginner

What does the worker_connections directive control in nginx?

It defines the maximum number of simultaneous connections each worker process can handle. This limits how many clients can be served at the same time per worker.

intermediate

How do worker_processes and worker_connections work together?

The total maximum connections nginx can handle is roughly worker_processes × worker_connections. More workers and connections mean nginx can serve more clients simultaneously.

intermediate

Why should worker_processes usually match the number of CPU cores?

Matching worker processes to CPU cores helps nginx use the server's hardware efficiently, avoiding too many processes competing for CPU time and improving request handling speed.

beginner

What happens if worker_connections is set too low?

Nginx will limit the number of clients it can serve at once, causing some requests to wait or fail under high load, reducing server responsiveness.

What does the worker_processes directive specify in nginx?

A Number of worker processes to start

B Maximum connections per worker

C Number of CPU cores to use

D Timeout for client connections

worker_processes sets how many worker processes nginx will start to handle requests.

If you want nginx to handle more simultaneous clients, which directive should you increase?

A worker_processes

B client_max_body_size

C worker_connections

D keepalive_timeout

worker_connections controls how many connections each worker can handle at once.

What is a good rule of thumb for setting worker_processes?

A Match the number of CPU cores

B Set to 100

C Set to the number of clients

D Set to 1 always

Setting worker_processes to the number of CPU cores helps use hardware efficiently.

How do you calculate the approximate max simultaneous connections nginx can handle?

A worker_processes / worker_connections

B worker_processes + worker_connections

C worker_connections - worker_processes

D worker_processes × worker_connections

The total max connections is roughly worker_processes multiplied by worker_connections.

What might happen if worker_connections is too low during high traffic?

A Nginx will crash

B Requests may queue or fail

C CPU usage will spike

D Memory usage will drop

Low worker_connections limits simultaneous clients, causing delays or failures.

Explain how worker_processes and worker_connections affect nginx's ability to handle client requests.

Think about how many clients nginx can serve at once.

Describe why matching worker_processes to CPU cores is important in nginx configuration.

Consider how CPU cores and processes work together.

Practice

1. What does the worker_processes directive control in an nginx configuration?

easy

A. The timeout for client connections

B. The maximum size of client request body

C. The number of server blocks defined

D. The number of worker processes handling client requests

Solution

1. Step 1: Understand the role of worker_processes

   This directive sets how many worker processes nginx will start to handle incoming requests.

2. Step 2: Compare with other options

   Other options relate to different settings like request size, server blocks, or timeouts, not worker count.

3. Final Answer:

   The number of worker processes handling client requests -> Option D

4. Quick Check:

   worker_processes = number of workers [OK]

Hint: worker_processes = how many workers run [OK]

Common Mistakes:

• Confusing worker_processes with worker_connections
• Thinking it controls timeout or request size
• Mixing it with server block count

2. Which of the following is the correct syntax to set worker connections to 1024 in nginx?

easy

A. worker_connections = 1024

B. worker_connections 1024;

C. worker_connections: 1024

D. worker_connections(1024);

Solution

1. Step 1: Recall nginx directive syntax

   nginx directives use the format: directive_name value; without equals or parentheses.

2. Step 2: Identify correct syntax

   worker_connections 1024; matches this format exactly with a semicolon ending.

3. Final Answer:

   worker_connections 1024; -> Option B

4. Quick Check:

   nginx directives end with semicolon [OK]

Hint: nginx directives end with semicolon, no equals [OK]

Common Mistakes:

• Using equals sign (=) in directive
• Using colon (:) instead of space
• Adding parentheses around values

3. Given the following nginx config snippet:

worker_processes 2;
worker_connections 512;

What is the maximum number of simultaneous connections nginx can handle?

medium

A. 512

B. 256

C. 1024

D. 2

Solution

1. Step 1: Understand the meaning of directives

   worker_processes = 2 means 2 workers; worker_connections = 512 means each worker can handle 512 connections.

2. Step 2: Calculate total connections

   Total connections = worker_processes * worker_connections = 2 * 512 = 1024.

3. Final Answer:

   1024 -> Option C

4. Quick Check:

   2 workers x 512 connections = 1024 [OK]

Hint: Multiply workers by connections per worker [OK]

Common Mistakes:

• Using only worker_connections value
• Using only worker_processes value
• Adding instead of multiplying

4. You set worker_processes 4; and worker_connections 1024; but nginx only handles about 1024 connections total. What is the likely cause?

medium

A. The OS limit on open files is too low

B. worker_processes must be set to 1

C. worker_connections must be less than 512

D. nginx does not support multiple workers

Solution

1. Step 1: Understand expected max connections

   With 4 workers and 1024 connections each, max should be 4096 connections.

2. Step 2: Identify system limits

   OS limits on open files (ulimit) can restrict max connections nginx can open, causing lower actual limits.

3. Final Answer:

   The OS limit on open files is too low -> Option A

4. Quick Check:

   OS file descriptor limit affects max connections [OK]

Hint: Check OS file limits if max connections too low [OK]

Common Mistakes:

• Assuming nginx ignores worker_processes
• Reducing worker_connections unnecessarily
• Believing nginx can't use multiple workers

5. You want nginx to handle at least 10,000 simultaneous connections. Your server has 4 CPU cores. Which configuration is best to achieve this?

hard

A. worker_processes 4; worker_connections 2500;

B. worker_processes 1; worker_connections 10000;

C. worker_processes auto; worker_connections 2000;

D. worker_processes 10; worker_connections 1000;

Solution

1. Step 1: Understand requirements

   To handle at least 10,000 connections on 4 CPU cores, set worker_processes to 4 (matching cores) and calculate worker_connections accordingly.

2. Step 2: Calculate for worker_processes 4; worker_connections 2500;

   worker_processes 4; worker_connections 2500; gives 4 * 2500 = 10,000 connections.

3. Step 3: Compare other options

   B uses 1 worker (poor performance); C with auto (4 workers) * 2000 = 8,000 (insufficient); D uses 10 workers (overhead).

4. Final Answer:

   worker_processes 4; worker_connections 2500; -> Option A

5. Quick Check:

   workers (cores) * connections >= 10,000 [OK]

Hint: Match CPU cores for workers, tune connections to meet target [OK]

Common Mistakes:

• Using single worker (poor performance)
• Setting insufficient connections per worker
• Oversubscribing workers beyond cores