Thanks Reinis. The system is ARM-based server development platform. The chip is essentially a Pass 1 prototype (with known limitations) - not a production partby stevewin - Nginx Mailing List - English
Thanks Maxim. Setting either 'accept_mutex pff;' or reuseport on the listen directive doesn't seem to change the general trend much (apologies for formatting below but can't seem to find a way to paste data elegantly in this forum) In data below the Columns are as follows "Wrk_threads" "Connections" "Default config" "access_log off';" "by stevewin - Nginx Mailing List - English
I am beginning to look at NGINX performance on a development system with traffic driven by Wrk. Initially I am just looking at static HTTP serving. I am using NGINX v1.10.1 running on the host system with Ubuntu 16.04. Wrk v4.0.4 is running from a separate client platform over a private 40GB connection. The CPU on the host system has 24 cores (no hyperthreading). I had started to look intby stevewin - Nginx Mailing List - English