changing php fpm config to the following allows me to have 4000-8000 concurrent connections at once and 0 failure rates.. after running numerous ab tests.. it is now in production and running 2 boxes side by side and accepting requests perfectly.. it's only about 30% ramped up due to proxy servers.. but hitting it with ab I was very stable. if anything thing changes I'll report back in this but aby JustaNginx - Php-fpm Mailing List - English
Updating the somaxconn to 10240 I was able to get the socket to work.. and I changed a few other things but see below for ref.. hope this helps others out there. Nginx config fastcgi_pass 127.0.0.1:9000; now is fastcgi_pass unix:/var/run/php5-fpm.sock; changed all the timeouts to 20 fastcgi_connect_timeout 20; fastcgi_send_timeout 20; fastcgi_read_timeout 20; FPM config listen = 127by JustaNginx - Php-fpm Mailing List - English
sractch this.. I was editing the wrong server.. this below doesn't work on sockets still getting the same problem with sockets being worse and IP being less worse.. happens about 10 seconds after the ab start. JustaNginx Wrote: ------------------------------------------------------- > update.. > > changing to > pm.max_requests = 500 > > I was able to get the sockeby JustaNginx - Php-fpm Mailing List - English
update.. changing to pm.max_requests = 500 I was able to get the socket to work the same as the IP.. I thought this meant something else.. but it means after 500 requests it'll respawn.. Tried doing 0 but gives same result as 500.by JustaNginx - Php-fpm Mailing List - English
I've got a server CentOS 6.4 32bit 16gig mem 300gig HD CPU - 8 cores 2.67ghz The problem I am having is I am trying to ab test I've done both this ab -v -k -r -n 5000 -c 200 http://172.16.33.46/?ip which results in this Server Software: nginx Server Hostname: 172.16.33.46 Server Port: 80 Document Path: /?ip Document Length: 873 bytesby JustaNginx - Php-fpm Mailing List - English