QuestionQ21

VerifiedCatalog and Products

An Adobe Commerce Architect finds that the product price index requires too long to run. The store is configured with multiple websites and dozens of customer groups.

Which two methods can the Architect use to reduce the full price-index execution time?

Choose two
Explanation

Enabling price index customer group merging lets the indexer collapse products that carry no tier pricing into a single shared row instead of generating a duplicate row for every customer group, which sharply cuts the number of rows the full price reindex has to build when there are dozens of groups. Setting the MAGE_INDEXER_THREADS_COUNT environment variable lets the price indexer run across multiple parallel threads/processes instead of a single thread, further cutting the wall-clock execution time on a catalog spanning multiple websites and customer groups.

Community Discussion

No comments yet. Be the first to start the discussion!