Hi Maxim, Thank you for your suggestion. I understand that enabling/disabling logging introduces extra CPU overhead. However, I will start to monitor the listen queue with the ss command and debug the Issue further. Thanks, Omby heythisisom - Nginx Mailing List - English
Hi Maxim, The nginx reverse proxy and uWSGI runs on the same host. Each nginx reverse proxies are connected to only one single Instance of the uWSGI backend. But in the uWSGI backend, I'm running 4 workers in total based on the configuration 2 workers can be handled by 1 VCPU. Essentially the Instance I run has 2 VCPUs hence It translates to 4 workers. The listen queue length of my backendby heythisisom - Nginx Mailing List - English
Hi Maxim, The nginx reverse proxy and uWSGI runs on the same host. Each nginx reverse proxies are connected to only one single Instance of the uWSGI backend. But in the uWSGI backend, I'm running 4 workers in total based on the configuration 2 workers can be handled by 1 VCPU. Essentially the Instance I run has 2 VCPUs hence It translates to 4 workers. The listen queue length of my backendby heythisisom - Nginx Mailing List - English