Skip to main content

Algolia DevCon - June 28-29, 2023

Discover the future of the AI Stack with Algolia, be the first to see new platform demos and announcements, and get the most out of Algolia through interactive workshops.

REGISTER FOR FREE DON'T SHOW AGAIN
×

How long does Algolia take to re-index changes in Magento?

  • Updated

There are a few key factors that can influence the time it takes to re-index changes to your Magento data such as:

  • how often you re-index to Algolia,
  • the number of items you are indexing,
  • the available resources on your server,

Generally speaking, if you use the SKU re-indexing form those items will be indexed quickly. However, if you send a large number of changes to Algolia, those changes will take time to build. Due to varying factors it's not possible provide an exact timeframe this will take and there is no guaranteed ETA.

To help with indexing speed, if you are using the indexing queue, make sure that it is configured to update at the correct rate required for your use case.

Below are some additional steps you can take to optimise the indexing process and avoid delays:

  • Upgrading to the latest version of the extension

    Our team is always working to optimise the extension's performance, so upgrading to a newer version will give you access to the newest features and improvements already implemented on the extension. For example, versions 3.18.1 and 3.17.4 introduced improvements on setSettings operations sent during indexing and configuration saving that can greatly decrease indexing times.
     
  • Eliminating the amount of full reindexing operations the extension runs on your environment

    Frequent full reindexing operations are often not needed and can cause unnecessary strain to server resources. Delta indexing automatically keeps your indices up to date and does not require time-consuming operations like saveSettings or moveIndex.

    Version 3.16.0 introduced the "Indexing Manager" tab, where you can disable automatic/unexpected full reindexing operations triggered by the extension. You can still trigger full reindexing operations when needed using CLI commands. 
     
  • Disabling the use of a temporary index during catalog reindex

    As of version 3.17.0 you can disable temp indexing on full reindex of your products index. This means that there will be no moveIndex tasks involved in your full reindexing operations and updates will start appearing in your index without waiting for the full reindex to complete. 
     

  • Optimise your batch size

    Version 3.17.0 also introduced the Batching optimizer feature, which dynamically determines the most efficient batch size, based on your data and cluster performance, to help you optimise your indexing build times.

Related articles