I’d suggest that you use wrk2, httperf, ab or similar to run a synthetic test. Can your site handle one request every five seconds? One request every second? Five every second? ... is your backend configured to log service times? Is your nginx configured to log service times? What do you see? By slowly ramping up traffic you will be able to see when and how the site transitions from healthy to unhealthy.
Sent from my iPhone > On Jul 16, 2019, at 8:48 AM, heythisisom <nginx-fo...@forum.nginx.org> wrote: > > 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, > Om > > Posted at Nginx Forum: > https://forum.nginx.org/read.php?2,284757,284868#msg-284868 > > _______________________________________________ > nginx mailing list > nginx@nginx.org > http://mailman.nginx.org/mailman/listinfo/nginx _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
