Big Day Release: Magento Full Cache

October 15, 2012 Yauheni Katkouski Magento
Big Day Release: Magento Full Cache

Magento Full Cache allows caching product, catalog and CMS pages, which makes it possible to minimize website load time for better user experience. Having the content cached will increase your site performance, as well as lower your server bandwidth requirements. Default Magento dynamic blocks as well as blocks admin configures in the extension settings are not cached. Customer information cannot be lost that way.

Key features:

  • Product, catalog and CMS pages caching
  • Possibility to exclude any dynamic block from caching
  • Caching both for authorized users and guests
  • Multi-currency and multi-language stores support
  • Easy debug and placeholder adding process

Let’s now review these features closer.

Caching is critical for speeding up web pages. Magento Full Cache will make your site fly like a rocket. When the page is loaded for the first time, the cache file is created and saved. On subsequent page loads it will be retrieved and sent to the requesting user.

Default Magento dynamic blocks are automatically excluded from caching. It’s possible to restrict caching of any dynamic block in the extension configuration.

Magento Full Cache doesn’t interfere with View as, Sort By

and Show per page functionality on catalog pages because user session data about a view mode is taken into account. The extension can use either File or Memcache caching system.

If the extension is installed properly, a new Cache Type “Full Cache” will appear in System -> Cache Management.

 

In extension settings, admin can configure placeholders – dynamic blocks, excluded from caching – to be highlighted on the front end. He/she also selects the cache Type: “files” or “memcached”.

 

In Expires field, cache lifetime in seconds is entered. If it is left empty or 0 (zero) is entered, cache will not be flushed until the corresponding process will not be launched.

In CMS Pages Cache, Сatalog Pages Cache and Product View Pages Cache menus, corresponding pages caching is enabled.

 

In Blocks to Ignore area, comma-separated list of dynamic block names to be excluded from caching is entered. The less blocks the field contains the faster cached pages load. Default Magento dynamic blocks are excluded from caching automatically, so there is no need to enter their names.

In Params to Ignore area, admin enters comma-separated list of get parameters. Pages with these parameters will be excluded from caching. It is useful for sites with referral and advertising links.

 

Let’s enable the Test Mode to get a general idea of how Magento Full Cache extension works.

When the page is loaded for the first time, the cache file is created and saved.

 

On subsequent page loads it will be retrieved and sent to the requesting user.

 

Visit the demo page read the user guide to see how the extension works.



3 comments

  1. Ryan, we have not compared our module with Varnish. I think the logic of these modules is different, so it’s difficult to compare…

  2. Ryan, in this case we should better compare FPC and Varnish.
    As you understand FPC can use memcached as a storage – distributed object caching system. Varnish – is a caching reverse HTTP proxy, and it sits in front of your Apache web server.

    In general for magento they do the same things – cache all the page not affecting dynamic blocks. If we need to choose the best way – from our experience:

    If the site is using mostly static pages without a lot of dynamic blocks (90/10 static to dynamic) – use Varnish. If it’s necessary to quickly generate a page with a lot of dynamic data – fpc and memcached is better. Don’t forget that for maintenance of the dynamic content in varnish you will have to create placeholders for each block.

Post a new comment

top
BelVG Newsletter
Subscribe to our mailing list and get interesting stuff and updates to your email inbox.
Email *