Make your store faster than light
Super fast response times and lower server load making your store more than 100x faster.
No need to worry about hole punching configs, WebCharger is based on LiteMage and takes care of everything. It’s faster out of the blocks than Varnish and integrates with Litespeed Web Server
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.
Page caching is the most powerful way to bypass Magento’s heavy architecture and speed up slow pages, but even though 95% of the content on a Magento page may be the same for all visitors (and is thus safe to cache), items in a shopping cart or the list of last viewed items, for example, cannot be cached and shown to all visitors. Because of these small blocks that change per-user, in our case Webcharger ustilies a private cache, but with WebCharger Enterprise we can hole punch these small block that need to be per user.
Say hello to hole punching
WebCharger Enterprise Cache uses Edge Side Includes (ESI) to punch holes in pages where information changes from visitor to visitor. The remaining content is saved to cache. When the next person visits the same page, the cached content is served quickly, with only the holes needing to be filled in with data for that visitor. WebCharger Cache also caches per-user data in private caches, so entire pages, even those with multiple holes, can be assembled completely from cache.
Click below to see what parts of the page are hole punched.
How Does WebCharger compare to other page caching solutions for Magento?
600 Req/Sec Litespeed + WebCharger
35 Req/Sec Apache + Turpentine (Varnish)
15 Req/Sec Nginx + Turpentine (Varnish)
9.3 Req/Sec Apache
8 Req/Sec Nginx
Varnish-based solutions (Turpentine, etc.)
- Complicated to set up.
- Requests dynamic blocks individually, multiplying the high cost of Magento framework initialization. Can make a cached page even slower than an uncached page.
- No SSL support. Frontend proxy server required to support HTTPS, adding even more layers.
- Uses AJAX, which lowers overall server performance.
PHP-based solutions (Full Page Cache)
- Content is cached by PHP, so all pages are still generated dynamically by PHP.
- PHP is a heavy language and overall scalability is thus limited by PHP scalability.
- Reliance on PHP causes generally slower page load times.
- Limits in PHP scalability make PHP solutions vulnerable to DDoS attacks.
- All content can be assembled from cache, even per-user, private blocks, for best performance.
- Multiple blocks are called for in a single request, lowering overhead.
- Native SSL support.
- Supremely scalable — handles 10,000’s of connections without missing a beat.
- Built-in extra anti-DDoS features protect you from attacks.