On Thu, 2005-05-26 at 14:53 -0400, Erik Aronesty wrote: > If all you're doing is serving static pages, you're probably not hanging > out on the modperl list. > > That being said, thttpd rocks, but it's cgi speed is awfully slow. > ppcgid kicks it's butt in that arena.
Multiplexing while running arbitrary perl code that does DBI fetches and other blocking tasks is not very easy. That's why most people who need more speed for static files use some kind of proxy setup (perlbal and tux do this) to send the dynamic stuff to mod_perl or just put the static files (i.e. images mostly) on a separate subdomain handled by the multiplexing server. > My business partner and I decided on two tactics: he started building a > patch to thttpd to run perl scripts natively as opposed to exec'ing, and > I built a pure perl web server. I finished first, so we're using that > for now. But I think that a perl patch to thttpd (including preloading > support) is what we'll be using in the long run... it's the right way to go. I think you'd be better off using a well-tested and supported tool like mod_perl for the dynamic stuff than trying to replicate it in another server, but I admit to being biased. - Perrin
