cancel
Showing results for 
Search instead for 
Did you mean: 

Index management best practice

SOLVED

Index management best practice

Hi all. In Magento 2.1 I wonder which mode is better and why, I mean "Update on Save" or "Update on Schedule". My questions:

1) Does "Update on Schedule" impose higher load on the server? I have a crontab setup correctly and it runs every minute, but reindexing every min is an overkill isn't it? Or is reindexing so smart it doesn't reindex if not necessary.

2) When/what does trigger the "Update on Save" mode? I mean does it fire on each change (add product, delete product, add attribute, change quantitiy....)

 

So in general which one do you suggest and why, please suggest, much thanks.

3 REPLIES

Re: Index management best practice

@tofi

 

In my opinion, it's best to "Update on Schedule" because index update may take a long time and if you've set it to "update on save" then it means that the server will have to reindex every time you make crud changes to the magento system. 

 

You can read more about indexes here: 

Magento 2 Indexing overview

Manage the indexers

Magento Certified Solution Specialist | Lead Magento developer
If this response was helpful to you, consider giving kudos to this post

Re: Index management best practice

Thanks for feedback ShoaibRehman89. I've read the docs, and if I understand correctly, reindexing process will start only if a certain indexer is in "Reindex Required" state. So that would mean, if I have "Update on Schedule" option enabled, cron will try to trigger reindexing process every minute, but if nothing needs to be reindexed, there won't be any heavy processing going on on the server. I was worrying, that some high load process would run every minute on the server, that's what I dont' want Smiley Wink

Thanks again.

Re: Index management best practice

@tofi

I am glad you found the solution. 

 

Let me know if you need any further help ! 

Magento Certified Solution Specialist | Lead Magento developer
If this response was helpful to you, consider giving kudos to this post