-
-
Save v0lkan/90fcb83c86918732b894 to your computer and use it in GitHub Desktop.
user web; | |
# One worker process per CPU core. | |
worker_processes 8; | |
# Also set | |
# /etc/security/limits.conf | |
# web soft nofile 65535 | |
# web hard nofile 65535 | |
# /etc/default/nginx | |
# ULIMIT="-n 65535" | |
worker_rlimit_nofile 65535; | |
pid /run/nginx.pid; | |
events { | |
# | |
# Determines how many clients will be served by each worker process. | |
# (Max clients = worker_connections * worker_processes) | |
# Should be equal to `ulimit -n / worker_processes` | |
# | |
worker_connections 65535; | |
# | |
# Let each process accept multiple connections. | |
# Accept as many connections as possible, after nginx gets notification | |
# about a new connection. | |
# May flood worker_connections, if that option is set too low. | |
# | |
multi_accept on; | |
# | |
# Preferred connection method for newer linux versions. | |
# Essential for linux, optmized to serve many clients with each thread. | |
# | |
use epoll; | |
} | |
http { | |
## | |
# Basic Settings | |
## | |
# | |
# Override some buffer limitations, will prevent DDOS too. | |
# | |
client_body_buffer_size 10K; | |
client_header_buffer_size 1k; | |
client_max_body_size 8m; | |
large_client_header_buffers 2 1k; | |
# | |
# Timeouts | |
# The client_body_timeout and client_header_timeout directives are | |
# responsible for the time a server will wait for a client body or | |
# client header to be sent after request. If neither a body or header | |
# is sent, the server will issue a 408 error or Request time out. | |
# | |
# The keepalive_timeout assigns the timeout for keep-alive connections | |
# with the client. Simply put, Nginx will close connections with the | |
# client after this period of time. | |
# | |
# Finally, the send_timeout is a timeout for transmitting a response | |
# to the client. If the client does not receive anything within this | |
# time, then the connection will be closed. | |
# | |
# | |
# send the client a "request timed out" if the body is not loaded | |
# by this time. Default 60. | |
# | |
client_body_timeout 32; | |
client_header_timeout 32; | |
# | |
# Every 60 seconds server broadcasts Sync packets, so 90 is | |
# a conservative upper bound. | |
# | |
keepalive_timeout 90; # default 65 | |
send_timeout 120; # default 60 | |
# | |
# Allow the server to close the connection after a client stops | |
# responding. | |
# Frees up socket-associated memory. | |
# | |
reset_timedout_connection on; | |
# | |
# Open file descriptors. | |
# Caches information about open FDs, freqently accessed files. | |
# | |
open_file_cache max=200000 inactive=20s; | |
open_file_cache_valid 30s; | |
open_file_cache_min_uses 2; | |
open_file_cache_errors on; | |
# | |
# Sendfile copies data between one FD and other from within the kernel. | |
# More efficient than read() + write(), since the requires transferring | |
# data to and from the user space. | |
# | |
sendfile on; | |
# Tcp_nopush causes nginx to attempt to send its HTTP response head in one | |
# packet, instead of using partial frames. This is useful for prepending | |
# headers before calling sendfile, or for throughput optimization. | |
tcp_nopush on; | |
# | |
# don't buffer data-sends (disable Nagle algorithm). Good for sending | |
# frequent small bursts of data in real time. | |
# | |
tcp_nodelay on; | |
types_hash_max_size 2048; | |
include /etc/nginx/mime.types; | |
default_type application/octet-stream; | |
## | |
# Logging Settings | |
## | |
# | |
# Use analytics to track stuff instead of using precious file IO resources. | |
# Disabling logging speeds up IO. | |
# | |
access_log off; | |
error_log /root/PROJECTS/logs/error.log crit; | |
## | |
# Gzip Settings | |
## | |
gzip on; | |
gzip_disable "MSIE [1-6]\."; | |
# Only allow proxy request with these headers to be gzipped. | |
gzip_proxied expired no-cache no-store private auth; | |
# Default is 6 (1<n<9), but 2 -- even 1 -- is enough. The higher it is, the | |
# more CPU cycles will be wasted. | |
gzip_comp_level 9; | |
gzip_min_length 500; # Default 20 | |
gzip_types text/plain text/css application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript; | |
## | |
# Virtual Host Configs | |
## | |
include /etc/nginx/conf.d/*.conf; | |
} |
Hi @v0lkan,
Unlike for the access_log
directive, error_log off;
does not disable the error logs.
error_log off;
would create a file named "off" for logging the errors within the default NGINX config files directory.
This is also mentioned in the NGINX blog post, in which it recommends specifying error_log /dev/null emerg;
in cases where "disabling" error logging is preferred :)
Thanks! :)
Good day @arnav13081994,
Yes, you've.
"client_body_buffer_size 10K;"
This directive sets the buffer size for storing the client request body. In this case, it is set to 10 kilobytes (10k). It determines the maximum amount of data that Nginx can temporarily store from the client while the request is being processed.
Since the client_max_body_size directive is set to 16 megabytes (miga), you should choose a client_body_buffer_size value that accommodates this maximum size.
Considering that Nginx uses memory for other purposes as well, you can allocate a buffer size slightly larger than the expected maximum request body size.
Folks;
I haven’t been updating this for a while, and this file should be considered a starting point, not the end-all-be-all.
Every production setup and server is different; you’ll need to benchmark your performance, tweak things on the go, and read the official docs.
Nowadays, I’m dealing with pure NGINX less and cloud load balancers more;
however, if I see anything worthwhile to add here or any change that can improve in a system-agnostic way, I’ll update the file.
One other remark: This file's particular use was for a very high-throughput system with relatively smaller payloads. If you have larger payloads, your memory utilization will increase, and having too high of a file limit can indeed crash the process due to memory pressure.
So, yep, lots of moving parts, yet I tried to document the file as best as I can.
Cheers.
Hi, checking up, i run a pterodactyl.io hosting company (MCST.IO), and ive ran into some issues regarding gzip for plugin module's for minecraft, im unsure if the issue is gzip or php-fpm, but in general should gzip just be disabled from nginx.conf ? unsure as default conf does not match my other node server configs at default.
Yes, I forgot to mention that. I assume that the reader would know about that.
In addition certain cloud vendors do not allow fiddling with the limits; so always verify that you have the limits as expected after you set them.