When does automatic partial reindexing actually run in Magento EE 1.13?

When does automatic partial reindexing actually run in Magento EE 1.13?

September 13, 2026 · Illustrated author avatarBy Stefan Bogdanescu
When does automatic partial reindexing actually run in Magento EE 1.13?

Magento EE 1.13: Understanding Automatic Partial Reindexing

Partial reindexing is one of the most significant improvements introduced in Magento Enterprise Edition (EE) version 1.13. This feature allows you to optimize your database performance by reindexing only the necessary data, rather than running a full index rebuild every time.

Let’s dive into the details of how this automatic process works and address some common questions about its implementation.

The Partial Indexing Process Explained

In Magento 1.13, most indexes are now configured to support partial indexing out of the box. This means that when you mark an index as ‘Update on save’, it will only update the relevant records in the index when a change occurs, rather than rebuilding the entire index.

This is particularly useful for large databases where partial updates can significantly improve performance compared to full reindexing operations.

The Role of Cron Jobs in Automatic Reindexing

Magento 1.13 introduced an asynchronous indexing process that allows reindexing tasks to be deferred and executed via a cron job. This means you no longer need to manually trigger the reindex command every time data is updated.

The documentation suggests that this process occurs either within the minute or according to your Magento cron job schedule (https://www.magentocommerce.com/knowledge-base/entry/ee113-indexing#reindex-options).

However, it’s important to note that this isn’t an existing cron job enabled by default. You need to ensure that the cron jobs are properly set up and running in your environment for automatic partial reindexing to work effectively.

Setting Up Cron Jobs for Automatic Indexing

To enable the cron job for asynchronous indexing, you’ll need to take a few steps:

  1. Configure the cron configuration file (cron.php) in your Magento installation. You can find detailed instructions on how to do this in the official Magento documentation: https://adobe-commerce.redoc.ly/2.3.7/tag/crons

  2. Ensure that the cron job is running according to your specified schedule. By default, the cron job runs every 5 minutes. If you haven’t modified the configuration, it should be already set up.

Identifying the Cron Job for Automatic Indexing

While the documentation suggests an existing cron job for automatic partial reindexing, it can be challenging to identify this specific process in the core code.

The index cleaner schedule appears to handle the clearing of old records from change log tables but does not seem to perform any actual indexing operations itself.

To find the relevant cron jobs, you might need to review the Magento cron configuration files and look for entries related to reindexing. Some examples include:

  • app/code/core/Mage/Catalog/etc/config.xml (for catalog indexers)
  • app/code/core/Mage/Index/etc/config.xml (for index management)

Best Practices for Managing Automatic Indexing

To ensure optimal performance and minimize database load, consider the following best practices:

  1. Monitor your cron logs: Regularly review the Magento cron log to check if any reindexing tasks are being executed as expected.

  2. Optimize indexing configurations: Configure your indexes appropriately by setting them to ‘Update on save’ or ‘Update by schedule’ based on their requirements and your store’s traffic volume.

  3. Schedule indexers wisely: Place your heavy indexers during off-peak hours to minimize the impact on site performance during peak times.

Conclusion

Automatic partial reindexing in Magento EE 1.13 is a powerful feature that can significantly improve database performance and site stability.

While the documentation hints at an existing cron job for automatic indexing, it’s crucial to understand that proper configuration of your environments’ cron jobs is necessary to utilize this feature effectively.

By following the best practices outlined above and monitoring your cron logs regularly, you can ensure optimal usage of partial reindexing in your Magento EE 1.13 store.

Remember, proper database optimization is key to maintaining a fast and responsive e-commerce platform. Don’t hesitate to seek professional assistance if you require further help with configuring your Magento environment.

For more information on Magento development best practices and performance optimization strategies, feel free to explore our resources at Laravel Company.

Magento 1 Indexing Database Performance

Our network