On Friday 08 April 2005 12:23, Shawn wrote: > work well with the newer threading model. But, the newer threading model > results in better performance and scalability (?).
... on MS Windows (and other similar OSes) where threads are far, far cheaper than fork/exec. this is not the case on Linux where the only real savings you get is in the increased sharing of memory pools between threads. but given the amount of memory an Apache process takes, especially against the amount of RAM in a given box (is anyone here running Apache in production on a box with <64MB of RAM?), this is a non-issue. threading creates concurrency issues so that your modules need to be thread safe; and it makes it impossible to kill "just that one problematic apache process". it really comes down to how many processes/threads you need versus the thread and process limits on your box. if that isn't an issue, i'd not even bother and stick with the multiprocess style. threads do make a lot of sense for other programming problems, so i'm not trying to say they are generally useless on Linux. just not particularly interesting for a web server like Apache on Linux. -- Aaron J. Seigo GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
pgpTojEMEdoU1.pgp
Description: PGP signature
_______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
