Allen Gilliland wrote:
Elias Torres wrote:
We have little control over each blog's performance and how
it affects the rest of the site.
this is definitely one of the things that is constantly churning in the
back of my mind as well. i have spent a fair amount of time working on
performance improvements for Roller and I think things have come a good
ways, but the one big black hole that I still perceive is in our
templating/rendering system.
as Elias said, we don't really have any control over it and a
potentially clueless (or malicious) user could really affect the whole
site. i'm not sure i have any ideas on what to do about that yet.
Aside from moving to a custom tag "front end" to Velocity or FreeMarker
that disallows the nasty cases, I'm not sure how to solve this problem,
either.
I assume large web hosts that allow custom PHP pages must have some way
of limiting their CPU utilization. They must use something to
limit/kill OS-level processes, since that is how PHP works. Is there
anything for Java that creates a limiter/watchdog for threads?
-- Sean
