Skip to main content

Edge Cache Introduction

When you login to your control panel you’ll notice the HudHosting Edge Cache feature. This is our custom management utility that gives you all the power in a couple of clicks.

 

What is the HudHosting Edge Cache?

Our system caches your website pages and assets so subsiquent visitors to your site recieve responses directly from memory. This avoids bootstrapping of your whole site, database queries, PHP runtime, etc and rockets your site pages back to your visitors. With Edge Cache enabled you can handle more traffic, more of the time and it's FREE with all our packages.

 

HudHosting Edge Cache Control Panel

 

The Standard HudHosting Edge Cache is already enabled by default, this ensures all your sites static assets such as js, css, images and pdf's, etc are served driectly from cache.

You can choose to deploy our Drupal optimised cache *and we highly recomend you do*. The Drupal Optimised Edge Cache will ensure your site can handle traffic spikes and genereal visitor traffic recieve blazing fast responce times from your Drupal app.

You can clean your Edge Cache data at any time, perfect for when developing and you want to see your changes straigh away.

 

 

Deploy HudHosting Edge Cache

 

 

If you run applicaitons alongside Drupal, such as forum software and want to deploy the Edge Cache. You may find the Drupal Optimised Edge Cache breaks your other application/site software. In this case you can exclude the path to your other application via the 'Excludes' feature.

This is also really useful if you have a critical page or section of information that must be updated in real time.

IMPORTANT: Limited use of this feature will ensure most of your stie pages are cached. You should really try to cache your high traffic pages and those that require lots of heavey lifting to load such as views.

 

Just type and click

 

In the example above, we've excluded /secure and are about to exclude /forum. Just enter th paths you absolutely must exclude fromt the cache.

Authenticated (logged in users) are already exlcuded from the cache. Even if the page is cached, users that have signed into your site will bypass the cache for that page and view the uncached version served by Drupal.