Why tuning handles high traffic in Nginx - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the maximum number of worker connections in nginx.

Nginx

worker_connections [1];

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

A512

B1024

C2048

D256

Attempts:

3 left

💡 Hint

Common Mistakes

Using too low a number limits traffic handling capacity.

The worker_connections directive sets the maximum number of simultaneous connections that can be handled by a worker process. Setting it to 1024 allows nginx to handle more connections efficiently.

2fill in blank

medium

Complete the code to set the number of worker processes to match CPU cores.

Nginx

worker_processes [1];

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

Aauto

B1

C4

D8

Attempts:

3 left

💡 Hint

Common Mistakes

Setting a fixed number that doesn't match CPU cores.

Setting worker_processes to auto lets nginx automatically set the number of worker processes to the number of CPU cores, optimizing performance.

3fill in blank

hard

Fix the error in the directive that sets the maximum number of open files.

Nginx

worker_rlimit_nofile [1];

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

A1024

B65536

C65535

D100000

Attempts:

3 left

💡 Hint

Common Mistakes

Using values too high or too low causing errors or limits.

The worker_rlimit_nofile directive sets the limit on the number of open files for worker processes. 65535 is a common safe maximum value.

4fill in blank

hard

Fill both blanks to configure nginx to use epoll and enable multi_accept.

Nginx

events {
    use [1];
    multi_accept [2];
}

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

Aepoll

Bon

Coff

Dkqueue

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong event method or turning multi_accept off.

Using epoll in the events block enables efficient event handling on Linux. Setting multi_accept on allows a worker to accept multiple connections at once, improving performance under high traffic.

5fill in blank

hard

Fill all three blanks to configure keepalive timeout and max requests.

Nginx

http {
    keepalive_timeout [1];
    keepalive_requests [2];
    client_max_body_size [3];
}

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

A65s

B100

C10m

D1m

Attempts:

3 left

💡 Hint

Common Mistakes

Setting too short timeouts or too small max body size.

keepalive_timeout 1m keeps connections alive for 1 minute, reducing overhead. keepalive_requests 100 limits requests per connection to 100 for stability. client_max_body_size 10m allows clients to send up to 10 megabytes, useful for uploads.

Practice

1. Why is tuning worker_processes important in NGINX for handling high traffic?

easy

A. It limits the number of users who can connect.

B. It reduces the size of files served by NGINX.

C. It allows NGINX to use multiple CPU cores to handle more requests.

D. It disables logging to improve speed.

Solution

1. Step 1: Understand worker_processes role

   The worker_processes setting controls how many worker processes NGINX runs, usually matching CPU cores.

2. Step 2: Connect worker_processes to traffic handling

   More worker processes mean NGINX can handle more simultaneous requests by using multiple CPU cores efficiently.

3. Final Answer:

   It allows NGINX to use multiple CPU cores to handle more requests. -> Option C

4. Quick Check:

   worker_processes = use CPU cores [OK]

Hint: More worker_processes means better CPU use for traffic [OK]

Common Mistakes:

• Thinking it limits users instead of increasing capacity
• Confusing it with file size or logging settings
• Assuming it disables features to improve speed

2. Which of the following is the correct syntax to set worker_connections to 1024 in NGINX configuration?

easy

A. worker_connections = 1024

B. worker_connections 1024;

C. worker_connections: 1024;

D. set worker_connections 1024;

Solution

1. Step 1: Recall NGINX directive syntax

   NGINX directives use the format: directive_name value; without equals or colons.

2. Step 2: Match syntax to worker_connections

   The correct syntax is worker_connections 1024; with a semicolon ending.

3. Final Answer:

   worker_connections 1024; -> Option B

4. Quick Check:

   NGINX directives end with semicolon [OK]

Hint: NGINX directives: name value; no equals or colon [OK]

Common Mistakes:

• Using equals sign (=) which is invalid
• Using colon (:) instead of space
• Missing semicolon at the end

3. Given this NGINX snippet:

worker_processes 2;
events {
  worker_connections 512;
}

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

medium

A. 512

B. 2048

C. 256

D. 1024

Solution

1. Step 1: Calculate total connections

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

2. Step 2: Understand meaning

   This means NGINX can handle up to 1024 simultaneous connections across all workers.

3. Final Answer:

   1024 -> Option D

4. Quick Check:

   2 workers x 512 connections = 1024 [OK]

Hint: Multiply worker_processes by worker_connections [OK]

Common Mistakes:

• Using only worker_connections value
• Dividing instead of multiplying
• Confusing connections per worker with total

4. You set keepalive_timeout 65; in NGINX but notice connections close too early. What is the likely problem?

medium

A. The directive is misspelled or placed in the wrong context.

B. NGINX does not support keepalive_timeout.

C. The value must be less than 60 seconds.

D. You need to restart the server for changes to apply.

Solution

1. Step 1: Verify directive spelling and context

   Keepalive_timeout must be spelled exactly and placed in the correct context (http, server, or location block).

2. Step 2: Understand effect of wrong placement

   If misspelled or in wrong context, NGINX ignores it, causing default timeout and early connection close.

3. Final Answer:

   The directive is misspelled or placed in the wrong context. -> Option A

4. Quick Check:

   Correct spelling and context needed [OK]

Hint: Check spelling and config block for directives [OK]

Common Mistakes:

• Assuming value limits must be under 60
• Thinking NGINX lacks keepalive support
• Forgetting to reload config after changes

5. To improve NGINX performance under heavy traffic, which combination of tuning is best?

hard

A. Set worker_processes to CPU cores, increase worker_connections, enable keepalive_timeout.

B. Set worker_processes to 1, disable keepalive_timeout, reduce client_max_body_size.

C. Disable worker_connections, set worker_processes to 1, increase client_max_body_size.

D. Set worker_processes to CPU cores, disable worker_connections, set keepalive_timeout to 0.

Solution

1. Step 1: Match worker_processes to CPU cores

   This allows NGINX to use all CPU power for handling requests.

2. Step 2: Increase worker_connections and enable keepalive_timeout

   More connections per worker and keepalive improve concurrency and reduce connection overhead.

3. Step 3: Avoid disabling important settings

   Disabling connections or keepalive reduces performance under high traffic.

4. Final Answer:

   Set worker_processes to CPU cores, increase worker_connections, enable keepalive_timeout. -> Option A

5. Quick Check:

   Use CPU cores + connections + keepalive for traffic [OK]

Hint: Use CPU cores, max connections, and keepalive for best traffic [OK]

Common Mistakes:

• Setting worker_processes to 1 limits CPU use
• Disabling keepalive harms performance
• Ignoring worker_connections limits concurrency