Sujet : Re: Apache + mod_php performance
De : ldo (at) *nospam* nz.invalid (Lawrence D'Oliveiro)
Groupes : comp.os.vmsDate : 24. Sep 2024, 22:28:39
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vcvau6$3bcrt$10@dont-email.me>
References : 1
User-Agent : Pan/0.160 (Toresk; )
On Tue, 24 Sep 2024 14:28:05 -0400, Arne Vajhøj wrote:
I am not impressed by Apache + mod_php performance on VMS.
I recall that Apache offers a choice of worker processes or worker
threads. I suspect mod_php is not thread-safe, so you have to use multiple
worker processes. And process creation on VMS is expensive.
I wonder how Nginx deals with this: I don’t think it can load the Apache-
specific mod_php, so it offloads PHP to a separate process and uses
“reverse proxying” (actually server-side proxying) instead.
Server-side proxying is the way to go, anyway: I use it for my Python code
now. It lets you manage your own process context, create your own
subprocesses/threads/tasks ... whatever you want.
And I can use WebSockets as well, which PHP has trouble supporting.