When you have tens of thousands of blog posts, a really impressive number of comments, and hundreds of hits per second on the database, it’s important to find the right strategy to keep the site available without the server exploding.
WordPress cache plugins are very popular, practically essential in any project, since they offer the possibility of reducing the load on the database by displaying the same content, updated, in a static way.
Most of this type of WordPress extension works the same way: it fetches the information from the database, generates a static HTML page, and displays it to visitors until it receives an order to update its content. Choosing the update time of said HTML page depends on several factors: number of visits, frequency of updating the main content, frequency of new comments on the article … variables that we will have to constantly analyze to configure the appropriate values and offer the best possible performance to the readers.
Among the most popular plugins we have:
A classic that includes three different ways to provide static content to our readers: Mod_Rewrite, PHP and Legacy caching. The last method is the least popular (it uses a cache system different from the usual and identified readers than the rest), so most end up betting on PHP (it does not require altering htaccess and it is fast for most situations) or Mod_Rewrite (requires altering htaccess, but is ideal for receiving spikes from unexpected visits).
W3 Total Cache
Much more difficult to configure than the previous option, although it is the most used among the great blogs around the world. It promises to increase the loading speed of any WordPress by up to 10 times, it can integrate with CDN networks, it offers a cache option for pages and databases, it can compress the size of JC and CSS files … the options menu that is generated inside WordPress is so extensive that it can be difficult for those who are just starting, so I prefer to frame it in the plugins section for those who have experience with the theme.
Here you have a fantastic article showing how to configure some of its sections and here is an ebook that deals exclusively and exclusively with this plugin.
It is not as popular as the previous two, but it is so simple to configure that it is worth trying when it is not required to specify as many variables.
It is recommended for cases in which the server does not have many resources, there being a simpler version still called Lite Cache.
The official page of this new option is at www.satollo.net/plugins/hyper-cache.
What is your experience with the cache plugin used in your WordPress?