• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question worker_connections are not enough

LucaB.

Basic Pleskian
Hi,
we have a Plesk 12.30 #60 with nginx. In this server (2CPU and 2GB RAM) are running 50 websites and this morning ngnix writes "worker_connections are not enough". In /etc/nginx/nginx.conf I've changed it from 1024 to 2048. it's enough? There are other parameters to be controlled?

The website will increase to 70 in a few days.

Luca
 
There is following formula for determining nginx worker_processes and worker_connections:

max_clients = worker_processes * worker_connections

Where worker_processes [number of processor cores], for instance:

# cat /proc/cpuinfo |grep processor
processor : 0
processor : 1
processor : 2
processor : 3
processor : 4
processor : 5

So,

worker_processes 6;

Thus, you can calculate the desired value for worker_connections
 
Back
Top