Path: ...!weretis.net!feeder9.news.weretis.net!panix!.POSTED.spitfire.i.gajendra.net!not-for-mail From: cross@spitfire.i.gajendra.net (Dan Cross) Newsgroups: comp.os.vms Subject: Re: Apache + mod_php performance Date: Fri, 27 Sep 2024 20:13:50 -0000 (UTC) Organization: PANIX Public Access Internet and UNIX, NYC Message-ID: References: <66f70712$0$711$14726298@news.sunsite.dk> Injection-Date: Fri, 27 Sep 2024 20:13:50 -0000 (UTC) Injection-Info: reader1.panix.com; posting-host="spitfire.i.gajendra.net:166.84.136.80"; logging-data="14655"; mail-complaints-to="abuse@panix.com" X-Newsreader: trn 4.0-test77 (Sep 1, 2010) Originator: cross@spitfire.i.gajendra.net (Dan Cross) Bytes: 2981 Lines: 60 In article , Arne Vajhøj wrote: >On 9/27/2024 3:40 PM, Dan Cross wrote: >> In article <66f70712$0$711$14726298@news.sunsite.dk>, >> Arne Vajhøj wrote: >>> On 9/27/2024 3:16 PM, Dan Cross wrote: >>>> In article , >>>> Arne Vajhøj wrote: >>>>> On 9/26/2024 11:44 AM, Dan Cross wrote: >>>>>> In article , >>>>>> Arne Vajhøj wrote: >>>>>>> It must be Apache. >>>>>>> >>>>>>> Apache on VMS is prefork MPM. Yuck. >>>>>>> >>>>>>> MaxSpareServers 10 -> 50 >>>>>>> MaxClients 150 -> 300 >>>>>>> >>>>>>> actually did improve performance - double from 11 to 22 >>>>>>> req/sec. >>>>>>> >>>>>>> But the system did not like further increases. And besides >>>>>>> these numbers are absurd high to handle a simulator doing requests >>>>>>> from just 20 threads. >>>>>>> >>>>>>> But not sure what else I can change. >>>>>> >>>>>> My guess is that communications overhead is slowing things down. >>>>>> What happens if you set these super low, ideally so there's a >>>>>> single process handling requests, then see what sort of QPS >>>>>> numbers you get for your trivial text file. >>>>> >>>>> I set it down to 1. >>>>> >>>>> 0.1 req/sec >>>> >>>> So a single request takes 10 seconds? Or you can only make one >>>> request every 10 seconds, but the time taken to process that >>>> request is relatively small? >>> >>> It is throughput. >>> >>> N / time it takes to get response for N requests >>> >>> With 20 threads in client then there will always be 20 outstanding >>> requests. >> >> How long does it take to serve a single request? > >Based on the above information it should be 200 seconds. > >But it is actually more like 340 seconds. So apparently the 0.1 >req/sec is rounded up a bit. Ok, just to clarify, you hit the web server with a single request for a small static resource, while no other traffic was hitting it, and that request took more than _five minutes_ to complete? - Dan C.