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.