Why Magento 2 Price Reindexing Is Slow and How to Address It

Magento 2's price indexer is widely considered the slowest and most resource-intensive indexer in the platform, scaling poorly as catalog size grows. Rather than storing final prices directly, Magento precomputes effective prices — accounting for tier prices, customer groups, catalog rules, and special pricing — and writes them to the catalog_product_index_price table. This results in one row per product per website per customer group, meaning a 50,000-SKU store across two websites and four customer groups can generate 400,000 or more index rows before factoring in configurable product options. The catalog price rules engine compounds the problem, as it must evaluate every product against every rule's conditions on each reindex rather than performing a simple database lookup. Changelog-based incremental indexing via Mview can help on moderate stores, but heavily written catalogs risk falling behind and triggering costly synchronous rebuilds mid-request.