Re: Apache prefork overload caused by Googlebot crawling many host-routed sites

Thank you very much for your reply.

I had thought that one of the reasons why there has been a recent trend of migrating to other HTTP servers is that even mod_php adapted to multi-threaded operation cannot operate stably for a long period on multi-threaded MPM of Apache HTTP server.
I have also already tried using php-fpm with lighttpd.
However, if the use of mod_php is no longer recommended with the multi-threaded MPM of the Apache HTTP Server and the use of FastCGI is recommended, there is no need to change the front-end HTTP server.
Is it correct to understand it that way?

Regards.

On 2026/02/27 10:01, Frank Gingras wrote:
> On Thu, Feb 26, 2026 at 7:02 PM Tatsuki Makino <[email protected]>
> wrote:
>> When combined with PHP and the like, it sometimes causes unexpected
>> terminations, doesn't it?
>>
> Mixing httpd with the mod_php DSO is really not the best way to deploy a
> server.  What you want instead is to use a threaded mpm like event, and
> proxy to pools of php-fpm processes using proxy_fcgi.
> 
> This allows for a very large number of httpd workers, and a relatively
> limited number of fpm processes.  Then, you can apply caching as needed to
> prevent requests from tying up fpm workers for too long, and over-spawning
> heavy processes.
> 
> Back then when using prefork and mod_php, memory leaks did indeed occur
> over time, so restarting the workers was needed.  This is really no longer
> a major concern.
>