Worker processes and connections in Nginx - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the number of worker processes to 4.

Nginx

worker_processes [1];

Drag options to blanks, or click blank then click option'

Aauto

B8

C4

D1

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'auto' instead of a number when a fixed number is required here.

The worker_processes directive sets how many worker processes Nginx will use. Setting it to 4 means Nginx will run 4 worker processes.

2fill in blank

medium

Complete the code to set the maximum number of simultaneous connections per worker to 1024.

Nginx

events {
    worker_connections [1];
}

Drag options to blanks, or click blank then click option'

A512

B1024

C2048

D256

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a value too low that limits connections unnecessarily.

The worker_connections directive inside the events block sets the maximum number of simultaneous connections each worker process can handle. Setting it to 1024 allows each worker to handle up to 1024 connections.

3fill in blank

hard

Fix the error in the configuration line to correctly set worker processes to automatically match CPU cores.

Nginx

worker_processes [1];

Drag options to blanks, or click blank then click option'

Aauto

Bautomatic

Ccpu

Dcores

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'automatic' or 'cpu' which are not valid keywords.

The correct keyword to automatically set worker processes to the number of CPU cores is auto. Other options are invalid and cause errors.

4fill in blank

hard

Fill both blanks to set worker processes to 2 and worker connections to 2048.

Nginx

worker_processes [1];
events {
    worker_connections [2];
}

Drag options to blanks, or click blank then click option'

A2

B1024

C2048

D4

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up the values for worker processes and worker connections.

Setting worker_processes to 2 means Nginx will run 2 worker processes. Setting worker_connections to 2048 allows each worker to handle up to 2048 simultaneous connections.

5fill in blank

hard

Fill all three blanks to configure worker processes to auto, worker connections to 512, and set multi_accept to on.

Nginx

worker_processes [1];
events {
    worker_connections [2];
    multi_accept [3];
}

Drag options to blanks, or click blank then click option'

Aauto

B512

Con

Doff

Attempts:

3 left

💡 Hint

Common Mistakes

Setting multi_accept to 'off' when 'on' is needed for performance.

Setting worker_processes to auto lets Nginx detect CPU cores. worker_connections set to 512 limits connections per worker. multi_accept on allows a worker to accept multiple new connections at once, improving performance.

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