News for hackers. Stuff that matters.
Re:Ask HN: How did you learn about the design/architecture o... by davidw on Tuesday July 13, 2010 @06:24AM (#1510927)
Apache does not spawn a new thread for every request.
Re:Ask HN: How did you learn about the design/architecture o... by jaydub on Tuesday July 13, 2010 @07:42AM (#1511028)
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

Re:Ask HN: How did you learn about the design/architecture o... by pkghost on Tuesday July 13, 2010 @03:05PM (#1512389)
thanks for the explanation :)