Re: Upcoming time boundary events

On 6/2/2025 8:36 PM, Lawrence D'Oliveiro wrote:

On Mon, 2 Jun 2025 09:25:22 -0400, Arne Vajhøj wrote:

On 6/1/2025 11:44 PM, Lawrence D'Oliveiro wrote:

>
What about multiple concurrent connections? You can’t avoid creating
extra processes in that situation.

>
True.
>
But they will all be kept around and reused. OSU HTTPD use it for CGI
scripts - it works.

 But there’s a resource-usage cost associated with keeping processes in
existence, isn’t there. As opposed to letting the server process control
for itself how it will divide up multiple concurrent connections among a
set of service processes/threads.

It is a tradeoff between memory usage by having processes standby
and CPU usage of having to start new processes.

(I know, CGI doesn’t give you that control anyway. This is why Web
developers don’t like to use CGI nowadays.)

I would say that the main reason for CGI being obsolete is poor
performance. Process creation, image activation and IPC adds crazy
overhead.
Arne