There are several solutions that we can recommend to address this situation.įirst, Commerce allows you to configure separate cache storage for each cache type. Sometimes one Redis instance is not enough to serve incoming requests. To decrease indexation time, you can exclude certain websites from customer groups (shared catalogs). This is because by default, all websites are assigned to all customer groups (shared catalogs). Limit customer groups and shared catalogs by websitesĪ large number of product SKUs, websites, customer groups, or shared catalogs will impact the running time of the Product Price and Catalog Rule indexers. In this case, editing your MySQL configuration file and allocating more memory to the TMP_TABLE_SIZE and MAX_HEAP_TABLE_SIZE configuration values (the default is 16M for both) will improve performance for this indexer, but will result in MySQL consuming more RAM. Merchants with a large number of catalog rules need to adjust their MySQL configuration to optimize indexing time. We have not enabled batching for the catalog rules indexer. This reduces the full indexing time from 4 hours down to 2 hours with a default MySQL configuration. In some situations, we have seen significant decreases in indexing time.įor example, if you are running a profile similar to B2B Medium, you can override the configuration value batchRowsCount in app/code/Magento/catalog/etc/di.xml and override the default value of 5000 to 1000. This controls how many entities are processed at a time by the indexer. You can tune indexer performance by adjusting the index batching size variables. Category Product Index (Catalog Module).The following indexes support this feature:

To manage this setting, edit the batchRowsCount parameter in the di.xml file of the corresponding module. This way, the user can tune batch sizes based on the type and size of data in the database. The Commerce team selected the most loaded indexes and enabled batch indexing, which allows you to set a portion of data to be processed on each iteration. When dealing with large amounts of data, re-indexing can become a concern. This section covers best practices and recommendations on configuring Commerce to work with large amounts of data, extreme load, and other enterprise cases.

Commerce is a highly flexible and scalable product containing solutions for merchants of all sizes.

Advanced setup