> 30 jan. 2016 kl. 18:42 skrev D'Arcy J.M. Cain <da...@vybenetworks.com>: > > On Sat, 30 Jan 2016 18:33:56 +0100 > MiB <digital.disc...@gmail.com> wrote: >> 30 jan 2016 kl. 11:42 skrev D'Arcy J.M. Cain <da...@vybenetworks.com>: >> >>> Have you considered checking your database access? WP sites >>> basically get all their content from a MySQL database.If the >>> database is slow that will slow down your site. >> >> Well, this shouldn’t be true for server cached URL’s, would it? With > > Not sure why not. As far as the server is concerned the pages are > dynamic. How would it know whether anything changed? It's only static > pages that can be cached.
I’m glad you asked. This is not how a well made server cache works. The fundamental idea behind a server cache is to render pages and update the cached page in question only when you make changes to the source. A web app that can’t keep track of this isn’t a web app, it’s a hack. Read up: "caches the pages of your WordPress blog and delivers them without accessing the database… WP Super Cache gets around that. When it is installed, html files are generated and they are served without ever invoking a single line of PHP." http://z9.io/wp-super-cache/ "How to cache Wordpress DB so it doesn't Query MySql?" http://stackoverflow.com/questions/15622440/how-to-cache-wordpress-db-so-it-doesnt-query-mysql ______________________________________________________________________ css-discuss [css-d@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/