More and more hosting providers are providing server or account level caching these days. Siteground for example has several caching methods available to enable in the control panel itself. I dont know how they do this, but realise there is nothing in Virtualmin that can offer this. So we enable caching within the website itself, but am sure that would be more resource intensive having every site process its own caching than some sort of server/account level caching.
Its similar to HTTP/2, this is just built in for many hosting providers these days, yet seems I cant do it on my Virtualmin (I am on Centos 7).
So lately I have been feeling my competitiveness is decreasing whilst using Virtualmin, I cant offer the same hosting services than other companies.
So anyone know if there is anything to add to Virtualmin to offer this service? Or if we want it do we consider moving to a hosting company like Siteground which provide all these things on their dedicated servers within their control panels, and abandoning Virtualmin?
Look like they offer “server” caching and “wordpress caching”.
Its marketing wank in my book. If your server has enough memory, everything is cached to memory anyway. Depending on your file system, you could also cache to nvme or ssd. But that’s back end stuff, has nothing to do with virtualmin.
As far as WP-cache, that would have to be done per site not globally. So is as simple as copying your preferred wp-cache plugin folder upon WP install.
Not bashing them, just saying, you can do it all yourself. For free. Well, except for adding more memory obviously.
there are caching options…this has nothing to do with Virtualmin though. caching is a server function as you said.
I can think of a couple of linux based examples that are well known in the industry, these are Varnish and Litespeed (open source version), however, a bit of googling also shows there are quite a few others:
litespeed (the free open source version is very restrictive)
JCS (for Java server side applications)
I think that these days most people are more interested in using Clouflare CDN. All web browsers cache static content anyway
As an example, clear your web broswer cache, then open a website that has lots of media content and you know isnt cached (such as one on your own server). whilst initially it may take a few moments to load, as you repeatedly cycle through the webpages the site speed will increase over a few minutes until its loading almost instantaneously (because the media files have been stored on your system by your web browser…unless you have disabled this functionality in web browser of course)
the trick is getting the first time visitors browsing speed up…and that is where cloudflare comes in. It allows a low latency connection between end user and cached content on the cloudflare network. The added advantage of such an option being that your VPS doesnt use up precious resources trying to cache ridiculous amounts of content in memory waiting for someone to access it!
I havent done the figures, but i wonder which would be cheaper…paying for more RAM on your VPS in order to run Varnish or, paying for a cloudflare subscription?