Every request does not require a thread to be spawned (depends on configuration/load), but every connection would require its own thread. "The worker MPM uses

Every request does not require a thread to be spawned (depends on configuration/load), but every connection would require its own thread. "The worker MPM uses multiple child processes with many threads each. Each thread handles one connection at a time. Worker generally is a good choice for high-traffic servers because it has a smaller memory footprint than the prefork MPM. The prefork MPM uses multiple child processes with one thread each. Each process handles one connection at a time. On many systems, prefork is comparable in speed to worker, but it uses more memory. Prefork's threadless design has advantages over worker in some situations: it can be used with non-thread-safe third-party modules, and it is easier to debug on platforms with poor thread debugging support." http://httpd.apache.org/docs/2.0/misc/perf-tuning.html http://httpd.apache.org/docs/2.0/misc/perf-tuning.html