2006-11-01 21:36:44.279497+00 by Dan Lyke 3 comments
I don't know what all of this has broken, but I looked at upgrading to Apache 2 and decided that I didn't want to go down the path of more complexity and bizarreness. So I've switched over to lighttpd aka "lighty".
Things will be slower for a little while 'til I switch to FastCGI, but I now have maintainable config files that I understand, and the resources devoted to basic web serving have dropped dramatically.
[ related topics: Free Software Flutterby Meta Open Source ]
comments in ascending chronological order (reverse):
#Comment Re: made: 2006-11-02 00:39:36.616815+00 by: Dan Lyke
Okay, apologies for all of the "now it's working, now it's not working". I think we're there, I think we're substantially faster than with mod_perl thanks to SpeedyCGI, but I'm sure there are glitches still to be worked out.
#Comment Re: made: 2006-11-02 00:56:29.556606+00 by: Dan Lyke
Just testing again, tried a FastCGI hack.
#Comment Re: made: 2006-11-02 16:24:42.251915+00 by: Dan Lyke
Huh. Okay, the wacky thing is that although I see occasional hiccups in performance, benchmarks show the SpeedyCGI implementation as fastest despite the lack of database connection pooling. Very curious.