Quote:
It's not recommended to use PHP5-FPM via unix socket for more than 300+ concurrent connections due to you will definitely get nasty error: sock failed (11: Resource temporarily unavailable) or connect() failed (11: Resource temporarily unavailable) depending on your version, (you may need to increase start_servers, or min/max_spare_servers), and and every 5th page will be return Error 502. By using tcp/ip as a handler you will get more stability but will loose around 10 connection on each 100 concurrent connection in performance.
And the other 2 tricky things to make it to run more smoothly is to gracefully restart PHP5-FPM every 9 minutes and clear the Query Cache on MySQL every 8 minutes. Again, the time depends on your load and content of your project.
|
That's interesting - maybe that was my problem when I gave it a go...
note though his article title is misleading, since the majority of those 2k active connections are keep alives and with a timeout of 60seconds (very high imo) is likely to be dead timeouts that will gracefully timeout. He has 200/s reads, which is still a lot but nothing apache couldn't handle easily.
fris if you have both setup, mind posting some benchmark test results with ab with same 100 concurrents?