> Hmmm...what about a variant of the proxied mod_perl?
>
> Picture a lite bulk front-end apache doing the usual stuff then
> proxying the mod_perl stuff back to a serverly (chargeably?)
> process-limited apache with a different httpd.conf per site?
>
> Nah, not good, you still have to budget a fair few meg per mod_perl
> site.
>
Yea, that's the problem as I see it..., modperl processes can be _huge_, so you
need a finite way to control with an absolute hand the size of those processes.
Due to other things you really need your own apache config too..., so there in
lies the problem. I mean you could just have a series of scripts which checked
up on the total mem consumption of each hosted users modperl and then just kill
them and send an email to the site owner, but this is a tre-crappy way to go.
That's whats cool about the VM, it distinctly only allows "X amount" of memory,
and then it digs into its own swap rather than tearing down everyone elses
modperl.
Shane.
