Brion Vibber writes:
On Wed, 17 Sep 2003, Nick Reinking wrote:
I'm curious as to the beta-ness of
mod_throttle on Apache 2.0. Apache
2.0 really isn't much faster than 1.3 (on UNIX systems with fast context
switching, such as Linux), if at all. Futhermore, the threading model
seen in 2.0 has resulted in a lot of modules behaving strangely (because
they haven't had adequate debugging time, most likely). If I had to
make a guess, that's what I would say is causing the current problems.
Well, we're running apache 1.3.28, and mod_throttle isn't on pliny.
Is there a reason we aren't using Apache 2? From a newbie's point of view,
2 is a bigger number than 1.3, so it must be better ;-). If the code is in
PHP, how would a newer version of Apache break the code?
Nick Reinking's proposal was to move from Apache 2 to 1.3. We already have
1.3. So why not try moving from 1.3 to 2?
And a few replies down, he also writes:
Wild speculation is welcome, particularly with
falsifiable hypotheses. :)
Okay, then what about thttpd (tiny/turbo/throttling http daemon)?
http://www.acme.com/software/thttpd/
"In typical use it's about as fast as the best full-featured servers
(Apache, NCSA, Netscape). Under extreme load it's much faster."
It supports CGI, and IIRC you can configure PHP as a CGI interpreter, so
will it not work (possibly with a few minor changes) with MediaWiki?
The only problem I can see is the /wiki/ RewriteRule, and that might
be solvable with a script /wiki that parses the PATH_INFO or whatever
and calls wiki.phtml with the right parameters.
At the least, thttpd can be installed on one server on a different port,
and, e.g., meta:80 can be redirected to meta:8080 by Apache, just to see
if thttpd _might_ work.
=====
Geoffrey
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com