What type of content are you serving? Are you using a single server? How much load are you expecting? How fast can your staff detect/react to problems? How stable is the code that mod_perl will be serving? How much time and/or money have you invested in staging and testing? Are money transactions involved? What is your true benefit from using apache2/mod_perl2? How much does stability effect your pocketbook?

I'm not asking for answers to these questions, just trying to indicate the variables involved. Without knowing any of the answers to those questions, my answer would be an emphatic NO.

Personally, there is only one equation that matters: mod_perl2_cash_advantage - mod_perl2_cash_risk = value If the result is positive, use mod_perl2.

()-()
 \"/
  `                                                     

Well well, that is a very good answer indeed. Most of the answers I can make are clearly in disadvantgage of mod_perl2.
Your final formulae is very good indeed and clearly makes me say..."NO" :-)

Owww, what that all you wanted to know ;-) I don't actually have tested it for performance, but for what I'm using it for it is very stable. But I don't stress the module to its max, so I could be wrong...

I'm also curious about any performance tests...

-- JaWi

"A chicken is an egg's way of producing more eggs."

Well as I said before, when serving static pages I had apache2 twice as fast as apache1 . THis should be taken careffully though cause I had just compiled apache2 whereas the Apache1 I used was the one provided with my distro, loaded with modules and probably not very well configured... but the change was impressive nevertheless.