WebCharger – Included free with all shared accounts
A private cache is only used by one client. Generally this applies only to a cache maintained by that client itself, though if you had a proxy that was only being used by one client (say you had a small LAN for your own use only and put a web proxy near the gateway) it would be possible to configure it to act as a private cache. Private caches do not offer quite as much scalability as public caches, but they do have certain important advantages over public caches:
They offer immense benefits to the user of that one client.
Almost every client on the visible web (that is, browsers, RSS readers, and other interactive user agents) and a very large number of those on the machine-only parts of the web (that is, spiders and clients of webservices) use a private cache of some sort. As such you can rely upon the presence of at least one cache being involved in almost everything you do on the web.
With some representations it may not be appropriate for public caches to cache them or to return those representations without re-validating them but perfectly acceptable for private caches to do so (e.g. anything which can only be seen by authorized users or which changes its representation depending upon who is looking at it). It can even be appropriate for encrypted documents to be so cached (though this requires one to be very sure as to the security of the cache itself, and so is generally not done
WebCharger is a cache, also known as a dynamic content cache, a server level caching system which helps improve performance for Magento websites with high traffic.
WebCharger has similar features as Apache mod_cache but implemented in a more efficient way, and works like Varnish. It is an output cache for dynamic contents, so the usage does not limit to PHP pages. Unlike Varnish, it is built into LiteSpeed web server, eliminating one layer of reverse proxy. Hence more efficient for static contents. The uniqueness of WebCharger cache is that it uses rewrite rules (either in configuration files or .htaccess) to control its behavior for maximum flexibility.
Private cache is for caching resources for individual specifically, instead of public shared. The purposes are:
Maintain a persistent cache for applications that do not have a shared cache.
Maintain a private persistent cache for specific groups of documents that are not to be shared among other applications.
WebCharger uses LiteMage starter plan, further upgrades are available by request.