I'm not sure if you're serious about that or not, however
- Since Apache2 you could change multiprocessing modules. The prefork MPM does the equivalent of apache1 and makes a number of forked off worker processes.
- Apache1/Apache2-prefork don't use one process per request unless you specifically request it to. Worker processes are retired after a number of requests (usually a couple hundred) as this helps to contain the impact of any memory leakage that may have been accidentally introduced etc
- Apache1/Apache2-prefork doesn't wait for a request to spawn the new worker processes, It spawns them in the background and hands incoming requests over to them. An incoming request doesn't have to wait for a worker process to spawn
- Though you can argue that windows is reasonably performant in general, one primitive that linux that's far faster is process creation. Processes are meant to be cheap in unix systems, and used as such.
- Separating things out into multiple processes helps to contain the effect of any bugs. Worker processes can crash all they want and won't impact the service as a whole.
I tend to use prefork MPM on servers for the isolation, unless I'm expecting a tonne of traffic, but by all means use the worker MPM, which uses a large amount of threads inside a single process.