On Tue, Sep 11, 2012 at 10:34 AM, Ray Hunter <[email protected]> wrote: > Have you looked at the queries in your database? You might be able to > optimize.
I'm with Ray on this one. Jumping straight into a caching solution isn't a good first step. 1. Confirm which pages, actions, or queries that are causing the most slowness. 2. See if you can optimize said bottlenecks. 3. Re-test, repeat at #1 For caching, it's best to start by deciding on a caching strategy first. What to cache and when? There are many options: * Cache complete output via a reverse proxy * Cache HTML output in your application * Cache Database queries * etc. Only after you have a caching strategy should you then work on the "How to cache" question. --lonnie _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
