What is WordPress Object Caching?
WordPress Object Caching is a mechanism that allows data to be temporarily stored in memory during a request, making it quicker to retrieve on subsequent requests. This can significantly improve the performance of a WordPress site by reducing the number of database queries and the amount of processing required to serve a page.
When Should You Enable Object Caching?
You should consider enabling object caching in the following circumstances:
High Traffic Websites
If your website experiences high traffic, object caching can reduce the load on your database and server, improving overall site performance and user experience.
Complex Queries
For websites with complex database queries, object caching can speed up data retrieval by caching the results of these queries.
Dynamic Content
If your site generates a lot of dynamic content that doesn’t change frequently, object caching can help deliver this content more quickly.
WP.pro’s Approach to Object Caching
WP.pro adheres to a principle of not pre-installing any plugins and delivers WordPress exactly as it is provided by WordPress.org. However, we do provision a fully functional Redis server with every site that you can use to enable persistent object caching.
How to Use the Built-in Redis Server
To take advantage of the built-in Redis server already provisioned by WP.pro, you can use an object cache plugin of your choice, such as the Redis Object Cache plugin. The plugin will automatically configure itself upon activation.
Potential Conflicts
WP.pro has deeply integrated database caching into its platform, providing query caching among other features. In some instances, this functionality can overlap with the capabilities of an object cache plugin, potentially increasing latency for certain queries. Whether to use object caching in addition to the built-in solution depends on your specific needs and should be decided by each customer. If you choose to implement an object cache, consider measuring the performance with database caching enabled and disabled (refer to the plugin's documentation to disable this part of its capabilities for your tests)