mod_php is faster at serving static content than mod_perl is ;)

I'll have to take your word for it, but since we are nitpicking i'd like to point out that we use non mod_XXXX enabled Apache servers to serve most of our static content here where i work. ;)

UPDATE: We have Apache2 servers on the front end and mod_perl enabled servers on the back end. It works great for us. :)

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

I'll have to take your word for it, but since we are nitpicking i'd like to point out that we use non mod_XXXX enabled Apache servers to serve most of our static content here where i work. ;)

That the server has the module loaded, does not mean these modules are used to handle the requests. If you're serving static files via per-request executed code, your design is seriously flawed. Having unequipped apaches handle the request does speed up things, though, because the memory footprint is smaller. However... why use the heavy weight Apache for static content if you have special arrangements for static content anyway?

Juerd # { site => 'juerd.nl', do_not_use => 'spamtrap', perl6_server => 'feather' }

Being marginally faster is no longer a big deal any more. There are too many more important things to worry about with a project today.