New Feature: RunCache

Introducing RunCache Purger

What Is RunCache?

Everyone wants a fast website and at RunCloud, we love fast websites. When you install RunCloud on your server, NGINX is a part of the stack and caching is turned on by default. When caching is enabled, NGINX will save responses in the disk cache and use them to respond to browser requests without having to proxy requests for the same content every time. This will reduce latency, offload repetitive CPU tasks from your server, and increase speed times as well as Time to First-Byte.

From the NGINX website itself:

A content cache sits in between a client and an “origin server”, and saves copies of all the content it sees. If a client requests content that the cache has stored, it returns the content directly without contacting the origin server. This improves performance as the content cache is closer to the client, and more efficiently uses the application servers because they don’t have to do the work of generating pages from scratch each time.

Within the past year or two, we noticed an issue that our users were having: they were not able to clear their NGINX cache in any easy way and it required you to be an advanced user with an abundance of knowledge of Linux terminal commands to clear the NGINX cache. The only way to really do this without that knowledge was to restart your server, which is usually not ideal for anyone who needs their website up and running 24/7.

While we definitely salute our users with the advanced knowledge they may have, RunCloud was established with developers from all backgrounds in mind: from beginner to expert. Thus, we have been working hard to bring you a new feature that will make life and running your website a lot easier.

The update will enable one-click NGINX Cache Purging directly through your RunCloud dashboard via WordPress one-click install only. You will no longer need to mess with anything through Linux terminal command line interface for server-side caching. The RunCache service will come with its own WordPress plugin to install which will allow you to control everything right from WordPress or the RunCloud Dashboard.

Once you have created a web application through the RunCloud dashboard, you will see new options available. To access these options, simply click on RunCache or General Settings in the RunCloud dashboard.

RunCache Settings

After you have installed a web app for WordPress, you will gain access to the RunCache page, but you will need more than the free plan to use it. By default, RunCloud will set the Cache Folder Size to 50 MB. If you have an abundance of SSD storage, you may want to increase this to at least 1 GB or 1024 MB.

You may also tell RunCloud to store the cache for as long as you wish with 0 being never, 60 being one hour, or even 1440 minutes which equals 24 hours, and is highly recommended if you wish to cache everything for at least a day.

RunCache Pre-Installation

When you get everything set up, you will gain access to RunCache within the RunCloud dashboard. You can purge the cache or remove the plugin directly from the your WordPress install. Without RunCache being installed, caching will still occur, but you will be unable to set limitations for your NGINX caching.

Although you can delete the plugin directly from WordPress, if you do decide to remove it, it is recommended that you remove it via the RunCloud Dashboard.

RunCache Post-Installation

Note: RunCache will not cache anything for logged-in WordPress users. As you gain more visitors, you will begin to see the amount of data cached for them. The larger, the better, which means your visitors are being served data directly from the cache rather than from the database, speeding up the delivery of all content on your website.

What Is RunCache Purger?

By default, the NGINX server will always try to cache everything in order to speed up queries and processes of the server and the CPU. Other than by code, this involved a very lengthy process of clearing the cache, detailed in this article: NGINX Caching Tutorial For WordPress. Unfortunately, this method was not only tedious, but did not accomplish the task it was intended to do.

The RunCloud team realized this was an issue for all of our users. To resolve it, the RunCloud devs were hard at work to correct the issue and made it even more simple for our users to clear the NGINX cache. All of the pains of trying to clear your cache are now taken away with our brand new plugin via RunCache Purger.

We will be launching it with a few basic options and releasing updates based on further feedback and other findings as we move forward. The WordPress plugin will be available as well as the RunCloud Purger through the RunCloud Dashboard.

Once installed, head over to WordPress and you will now see RunCache automatically installed as a plugin on the Administration bar.

RunCache Purger plugin located on the Administration Menu

Located within the Settings is the menu item for the RunCache Purger as well.

RunCache Purger located on the Settings Menu

Once you click into the RunCloud Purger, you will see a screen with a variety of options.

RunCache Purger WordPress Settings Dashboard

Within this screen, you may clear the cache for the Homepage upon New Posts and Pages and deleted posts. You can also set options to purge all cache content when content is published or comments are added or removed. The cache extends to clearing the cache for archives.

RunCloud will automatically setup Redis Object caching for you with this plugin. You may also choose to purge the Object Cache and enable or disable the RunCache Purger plugin to handle this for you. It is unlikely you have to change any settings for the Redis Server. In fact, it is advised that you do not change any of the Redis Server settings. Doing so may cause things to stop working.

While RunCloud has been hard at work to deliver this new feature, and it is technically out of beta, we still need users to continue testing and ensure everything is working properly. For any issues that may arise, please use the Support menu at the top and open a ticket. We are very excited to release this new feature and hope it is as useful to you as it has been for us.

Share This On
Share on facebook
Share on twitter
Share on linkedin
Share on reddit

8 thoughts on “New Feature: RunCache”

    1. Hey Mark, considering this has to do with the NGINX cache, which is caching at the server level, this should be compatible with multisites and a complimentary cache to WP Rocket.

      1. This is fantastic! I’ve been waiting to see what would come of the nginx caching on runcloud, and I can’t wait to try this out!!!!

    1. Hey Irwan, an interesting request, but it has been done before. Remember that RunCloud, ServerPilot, Moss, EasyEngine all setup their own Apache/NGINX stacks meaning they tweak their own files and then install them on your server the way they feel is the most optimized. With the RunCloud NGINX stack, caching is enabled by default at the server level, so if you wish to test it, you have to setup a server with a one-click install WordPress on it, such as DigitalOcean or Vultr, and then run your tests. Setup another server with RunCloud on it and run the same tests, and you should see a difference. Here’s an article where someone actually did the test: https://quvor.com/serverpilot-vs-runcloud-wordpress/.

  1. This is very interesting, I have been using the “old method” in all my websites, but what about updating from the past method to this one, and what about if we don’t desire to use one-click wp, and we wish to install WP manually.

    Is there any advice on how to migrate or how to use this new method if we installed wp previously or without one-click service.

Leave a Comment

Your email address will not be published. Required fields are marked *

You May Also Like

Scroll to Top