in reply to prevelance of mod_perl

I, like you, wanted the option of using mod_perl on a hosting site. But, of course, most providers don't offer it.

There are a small select number of dedicated mod_perl hosting providers, however I decided to go with an entire virtual private server (VPS) hosted at Linode in Los Angeles, USA, and then subsequently rented another VPS at ByteMark in London, UK. On the VPSs I can select exactly which Apache version I want to use and add on mod_perl at will.

When I was with IPowerWeb I actually found my CGI Perl pages executed quite quickly, I presume this is because their servers are reasonably powerful even though each one is hosting hundreds of sites.

But of course going with mod_perl gives significant advantages. But there are issues and risks as well:

I guess what I'm saying is that if you really want to do mod_perl, then the rewards require that you take some risks, and most standard cheap hosting companies don't want to take those kinds of risks!

Replies are listed 'Best First'.
Re^2: prevelance of mod_perl
by perrin (Chancellor) on Jun 04, 2008 at 16:49 UTC
    The standing advice about mod_perl and threads from the mod_perl community is to not use them if you have a choice. People on Windows have to use them, but on Linux you're better off using the prefork model. It actually uses less memory than the threaded model and avoids problems with CPAN modules that aren't threadsafe.

    Regarding the VirtualHost issue you mention, this is a pretty basic limitation of Perl: you can't run two different versions of the same module in one interpreter.