Varnish is a web application accelerator platform, which caches data for the sake of faster access. It is sometimes referred to as an HTTP reverse proxy too and it works between a web server and a browser. When a site visitor opens a certain page, the content is requested by the browser, and then the server handles this request and sends back the necessary information. If Varnish is enabled for a particular website, it will cache its pages on the very first request and in case the visitor accesses a cached page once more, the data will be delivered by the caching platform instead of the server. The increased load speed is an end result of the substantially faster response time that Varnish offers compared to any web server software. Of course, this doesn’t mean that the site visitors will keep being served the same content again and again, as any modification on any of the pages is reflected in the content that Varnish stores in its memory.
Varnish in Shared Hosting
You can unlock Varnish’s potential and enhance the speed of your websites regardless of the shared hosting
plan that you have chosen and you can enable and set up the content caching platform with several mouse clicks via the simple-to-use graphical interface offered by our advanced Hepsia Control Panel. During the procedure, you’ll be able to choose two different things – how many Internet sites will employ the Varnish caching platform, in other words – the number of instances, and how much information will be cached, in other words – the amount of system memory. The latter is offered in increments of 32 MB and is not linked to the number of instances, so you can use more instances and less memory and vice versa. In case you have lots of content on a certain Internet site and you win numerous visitors, more memory will give you a better result. You may also consider using a dedicated IP address for the sites that will use the Varnish platform. Hepsia will offer you easy one-click controls for switching off or rebooting any instance, for clearing the cache for each site and for checking elaborate logs.