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

--00000000000057027b064c06fd39
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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 - =D7=90=D7=9C=D7=99=D7=94=D7=95

Op ma 2 mrt 2026 om 08:13 schreef Tatsuki Makino <[email protected]=
m
>:

> Thank you very much for your reply.
>
> I had thought that one of the reasons why there has been a recent trend o=
f
> 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=E2=80=AFPM 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.
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

--00000000000057027b064c06fd39
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I may be wrong on this but I think people move to thi=
ngs like lighttpd for the HTTP/3 support.</div><div><br></div><div>Apache m=
pm-event=C2=A0+ php-fpm works great for my uses.</div><div><br></div><div>H=
TH,</div><div>Eliyahu - =D7=90=D7=9C=D7=99=D7=94=D7=95</div></div><br><div =
class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail=
_attr">Op ma 2 mrt 2026 om 08:13 schreef Tatsuki Makino &lt;<a href=3D"mail=
to:[email protected]">[email protected]</a>&gt;:<br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex">Thank you very much for =
your reply.<br>
<br>
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-threa=
ded operation cannot operate stably for a long period on multi-threaded MPM=
 of Apache HTTP server.<br>
I have also already tried using php-fpm with lighttpd.<br>
However, if the use of mod_php is no longer recommended with the multi-thre=
aded MPM of the Apache HTTP Server and the use of FastCGI is recommended, t=
here is no need to change the front-end HTTP server.<br>
Is it correct to understand it that way?<br>
<br>
Regards.<br>
<br>
On 2026/02/27 10:01, Frank Gingras wrote:<br>
&gt; On Thu, Feb 26, 2026 at 7:02=E2=80=AFPM Tatsuki Makino &lt;<a href=3D"=
mailto:[email protected]" target=3D"_blank">tatsuki_makino@hotmail=
.com</a>&gt;<br>
&gt; wrote:<br>
&gt;&gt; When combined with PHP and the like, it sometimes causes unexpecte=
d<br>
&gt;&gt; terminations, doesn&#39;t it?<br>
&gt;&gt;<br>
&gt; Mixing httpd with the mod_php DSO is really not the best way to deploy=
 a<br>
&gt; server.=C2=A0 What you want instead is to use a threaded mpm like even=
t, and<br>
&gt; proxy to pools of php-fpm processes using proxy_fcgi.<br>
&gt; <br>
&gt; This allows for a very large number of httpd workers, and a relatively=
<br>
&gt; limited number of fpm processes.=C2=A0 Then, you can apply caching as =
needed to<br>
&gt; prevent requests from tying up fpm workers for too long, and over-spaw=
ning<br>
&gt; heavy processes.<br>
&gt; <br>
&gt; Back then when using prefork and mod_php, memory leaks did indeed occu=
r<br>
&gt; over time, so restarting the workers was needed.=C2=A0 This is really =
no longer<br>
&gt; a major concern.<br>
&gt; <br>
<br>
<br>
---------------------------------------------------------------------<br>
To unsubscribe, e-mail: <a href=3D"mailto:[email protected]=
g" target=3D"_blank">[email protected]</a><br>
For additional commands, e-mail: <a href=3D"mailto:[email protected].=
org" target=3D"_blank">[email protected]</a><br>
<br>
</blockquote></div>

--00000000000057027b064c06fd39--