Posts: 31,872
Thanks: 689
Thanked 4,184 Times in 3,202 Posts
This setting has to be 1 if you use fcgi on a apache webserver as apache uses only one fcgi process per apache child. So setting this per client or site does not makes any sense, as this value has to be 1. Settingit to a value > 1 will just use more ram without any benefit, as the other fcgi childs will never be used.
Ok, thanks Till, I admit I don't know how fcgi works exactly, but I'd like to limit the max simultaneos connections for a site or group of sites and I thinked it should be easy with fcgi.
Hope you understood my english
Denis
Posts: 31,872
Thanks: 689
Thanked 4,184 Times in 3,202 Posts
Yes, set the number of fcgi processes started by mod_fcgi to 1. The reason is that apache mod_fcgi spawns already one process per apache child so that php does not have to spawn its own childs. If you would spawn more processes, then they will not get used by apache.
Posts: 31,872
Thanks: 689
Thanked 4,184 Times in 3,202 Posts
These are fcgi processes and not cgi processes. The difference is that CGI processes are started one per pageview and terminate afterwards while fcgi processes stay in memory and can process multiple pageviews.
I followed your advice and indeed it's working but I'm still a bit confused since on all other sites I've visited recommended settings are much higher for FcgidMaxProcesses. Is this a difference in setup or are others just being silly (since you answered apache won't take advantage of the spawned php processes?)
Recent comments
1 day 5 hours ago
1 day 14 hours ago
1 day 17 hours ago
1 day 18 hours ago
1 day 20 hours ago
1 day 21 hours ago
1 day 23 hours ago
2 days 29 min ago
2 days 16 hours ago
2 days 17 hours ago