On 13 Mar 2012, at 21:32, Perrin Harkins wrote:
>
> Turn on the template caching. It's basically free and will speed
> things up. Caching at the page level is the ultimate in terms of
> speed, but it will only be possible for pages that are not dynamic on
> a per-user basis. Template caching
On Tue, Mar 13, 2012 at 3:51 PM, Dan Axtell wrote:
> I understand the value of having one light-weight server for static content,
> and a reverse proxy back to a heavy-weight Apache with mod_perl, and I
> understand I can use something like Varnish or mod_cache to add a caching
> layer, but I'm w
On 03/13/2012 03:51 PM, Dan Axtell wrote:
The apps are mostly dynamic forms based on HTML::Template. H::T has some
caching options but they seem more aimed at CGI users. I could convert to
Template::Toolkit, which as I understand converts to compiled Perl code (which
would presumably mean that
Getting static assets (js, css, gfx) off your apache children is far more
important than anything else for scaling up to lots of concurrent users
IMHO. We use a pound load balancer to direct static reqs to nginx "cdn"
and all dynamic requests to apache backends.
Once you have that in place t
Hello,
I'm looking at upgrading some legacy code that runs under mod_perl with an eye
towards making it more scalable.
I understand the value of having one light-weight server for static content,
and a reverse proxy back to a heavy-weight Apache with mod_perl, and I
understand I can use some
