Can anyone simply explain what are the caching mechanisms and indexing processes in Magento Community and Enterprise Editions? There are some articles out there regarding this. But still what are the significant differences? And how they are differ in each editions?

  • 1
    Magento community not allows partial indexing and not allow full page cache May 9, 2015 at 18:41

2 Answers 2


Both editions index data in order to be able to retrieve it faster, for example, product pricing is stored in indexes so it doesn't have to be calculated each time it is needed.

Magento Community Edition does not provide partial indexing, so each time of indexing all data is reindexed, not just data which has changed, meaning it takes longer (sometimes MUCH longer depending on your server and number of products, categories, product data etc.).

Magento Enterprise Edition differs from Community Edition caching in that it offers full page caching, meaning the entire page is cached and so is able to be served faster and using less resources on your server.

Magento Community Edition does still provide some useful caching mechanisms such as caching layout and block and CMS HTML. It can also cache (and combine) javascript and CSS, as well as product images.

There are also some great free full page cache extensions you can use for Community Edition which actually provide faster caching that the Enterprise built in full page cache.

Take a look at Turpentine as an example of one:


Note: These differences have changed considerably since 1.9 and this answer may no longer be fully relevant for Magento 2.x branches.


Also worth mentioning and to add to @performadigital's answer, several of the indexes in EE run as a background process. Full Re-index processes run 70-80% faster than CE.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.