Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.os.vms Subject: Re: Apache + mod_php performance Date: Sun, 29 Sep 2024 22:57:11 -0000 (UTC) Organization: A noiseless patient Spider Lines: 16 Message-ID: References: <66f8183e$0$715$14726298@news.sunsite.dk> <66f8a44c$0$716$14726298@news.sunsite.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Mon, 30 Sep 2024 00:57:11 +0200 (CEST) Injection-Info: dont-email.me; posting-host="a1a02b051aaecb67c07f3c0a04f3a680"; logging-data="2021819"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+IKrkOkaRVWaFw2586ymNS" User-Agent: Pan/0.160 (Toresk; ) Cancel-Lock: sha1:8vFEufJBJuq0N/vzgb1FRPHFnYo= Bytes: 2019 On Sun, 29 Sep 2024 10:46:12 -0400, Arne Vajhøj wrote: > That is not how Apache prefork MPM works. If that’s not how it works, then how can you serve a client from more than one member of the worker pool? > And I don't understand the "put all the client context into shared > memory" either. Are you saying that if socket descriptors are put in > shared memory then any process that map that memory can use those > sockets???? No, but the shared-memory context can contain an index into a table of socket descriptors in private per-process memory. If the process trying to server a client context does not actually have a socket descriptor in the slot for that context, it can ask for one.