Re: [users@httpd] Apache prefork overload caused by Googlebot crawling many host-routed sites

[Tatsuki Makino <ta...@hotmail.com>]

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 <ta...@hotmail.com>
> 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.
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: [users@httpd] Apache prefork overload caused by Googlebot crawling many host-routed sites

[Tatsuki Makino <ta...@hotmail.com>]

Hello.

We know, there are images that have been built up in the past :)
CGI is slow because it forks a process for each request.
If it is a module of the Apache HTTP server, it is always on standby and continues running. For example, mod_perl or mod_php.
Since when did FastCGI become such an important IPC? :)

Not currently... but in the version I was using when I enabled HTTP/2 on the Apache HTTP server, the prefork MPM could not be used for the module for HTTP/2.
It's not just load issues, there are increasing situations where prefork MPM cannot be used.

Regards.

On 2026/03/02 18:12, E.S. Rosenberg wrote:
> I may be wrong on this but I think people move to things like lighttpd for
> the HTTP/3 support.
> 
> Apache mpm-event + php-fpm works great for my uses.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: [users@httpd] Apache prefork overload caused by Googlebot crawling many host-routed sites

["E.S. Rosenberg" <es...@gmail.com>]

I may be wrong on this but I think people move to things like lighttpd for
the HTTP/3 support.

Apache mpm-event + php-fpm works great for my uses.

HTH,
Eliyahu - אליהו

Op ma 2 mrt 2026 om 08:13 schreef Tatsuki Makino <tatsuki_makino@hotmail.com
>:

> 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 <
> tatsuki_makino@hotmail.com>
> > 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.
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>