3

Running Magento Enterprise 1.14.

My client makes very frequent changes to the content of their store. Things like new products, changing product details, prices, inventory, stock, images, etc. etc. Naturally, this means that the Magento cache and/or indexes have to frequently be refreshed.

This, in turn, has a knock-on effect on performance, because if the cache is being purged ten times a day, there's zero chance for any meaningful amount of cached data or cached full pages to accumulate.

Customers unlucky enough to view a page at the exact moment of a heavy reindex might also see some "funny" looking pages.

Is there a setup which would allow me to maintain a steady level of caching and indexing while still allowing users to make frequent changes?

Some notes:

  • I'm aware performance should not rely on the cache. That's not what this question is about.
  • I do use a FPC pre-warmer/crawler but to little effect.
  • I've considered deploying a staging server where changes could be made and then fully cached, then simply doing a bulk insert/update between the two Magento databases - stupid or potentially workable?
Improve this question
5
  • Magneto 1.14 has partial indexing built in, and if you're using the FPC properly then the invalidation of the cached items would rebuilt. Both should not require full reindexing or cache purging.
    – B00MER
    Commented Nov 15, 2015 at 1:04
  • async reindex and fpc should work as normal, you can even invalidate zend opcache per file. dont see any issues here
    – MagenX
    Commented Nov 15, 2015 at 10:48
  • @B00MER Can you elaborate on what you mean by using it properly, please? We just edit category products/prices/etc. then reindex but sometimes changes are not shown until cache is manually flushed.
    – WackGet
    Commented Nov 16, 2015 at 18:09
  • @MagenX The problem is the frequency of the edits. The cache is constantly being invalidated. Even if one category is changed then performance will suffer because non-cached pages are slow to load/re-generate.
    – WackGet
    Commented Nov 16, 2015 at 18:11
  • @WackGet Since my comment was getting to be too long, just made it into an answer. Let me know if you have questions.
    – B00MER
    Commented Nov 16, 2015 at 19:48

1 Answer 1

Reset to default
1

I would install Aoe_Templatehints and Aoe_Profiler and take a look at your blocks caching status of the areas that are frequently edited to make sure proper block cache keys are being used, as the FPC should notice the changes differ and invalidate its cache for rebuilding without intervention.

The new indexer in 1.13+ of EE has partial indexing which means there shouldn't be a need to do full re-indexes.

Some Related Questions/Answers:

Improve this answer
0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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