mod_perl without persistent interpreter state?

[pbdgny]

Hello,

When last I checked, mod_perl is not that great for a shared hosting environment.  Now I see that v.2 has accommodations for Apache vhosts, but it still looks like each site needs it's own full blown Perl interpreter sucking down memory.

Is there a way to configure mod_perl to act more like mod_php in that each request gets a "fresh" interpreter to work in?

I did a cursory search of the mailing lists, but did not find anything.

This way you avoid the standard CGI setup/tear-down cycle while still providing a way for many mutually  distrustful Perl applications to coexist on the same server. (i.e shared webhosting)

Additional performance boosts could come via:

1) Caching pre-parsed Perl "byte code" to disk/memory.
2) Provide a simple method for apps to "self-cache" in an initialized state after the first request.

Can this be done currently, and if not, does anyone else think it a good idea?

Thanks,
David