Our multi-tiered caching system guarantees that your site remains performs optimally on our platform. With our upcoming cache management feature, handling and purging cache will be a breeze! In this blog post, I’ll introduce the new cache management interface and provide a quick overview of how these components work together.
Maintenance
Before we can release the cache management feature, we must first update all the underlying WordPres containers. This will take place on Thursday, April 10th, starting around 01:00 UTC / 5 PM PDT / 02:00 CEST. The site rebuild process may take a few seconds to a minute per site. Once all sites have been updated, we’ll proceed to deploy the new interface.
Interface
And here it is! The new interface allows you to purge each cache layer, or to completely enable/disable them. While we recommend keeping all cache layers enabled for optimal performance, this feature is particularly handy for development purposes.
Under normal circumstances, manual cache purging shouldn’t be required. CloudFlare caches static assets like images, JavaScript, and CSS, while both Nginx and Redis cache management are handled by their respective plugins.
However, if you frequently find yourself needing to manually purge the cache, please reach out to us! We’d be more than happy to help you to find out why the cache isn’t being purged as it is supposed to.
Cache layers
Here’s a quick recap of our cache layers and their functions:
CloudFlare: Primarily, CloudFlare serves as our Content Delivery Network (CDN). It optimizes images and caches static assets to enhance site performance.
Nginx: Nginx is the web server responsible for handling web request, and executing and caching your site’s PHP code.
Redis: Redis, through the Object Cache Pro plugin, offers persistent object caching. In WordPress, an object cache stores database queries, resulting in faster response times and reduced CPU load on the database server.