Product price reindex takes too long with Magento 2.4.1 + MySQL 8.x + PHP 7.4 + nginx

[davidandersson1]

Hello,

We are facing issue on catalog_product_price reindex. reindex takes too long to complete or never completes.

Preconditions (*)

1. Magento version 2.4.0 or 2.4.1
2. MySQL version 8.x
3. PHP version 7.4
4. Total number of products = 400k (400000)
5. Total number of bundle products = 1000

Steps to reproduce (*)

1. Create 1000 bundled products with 15 options.
2. Create 1 bundled product with 30 options.
3. Set price_type equal to Dynamic, sku_type equal to Fixed, weight_type equal to Fixed on all bundle products.
4. Run price reindex from CLI: bin/magento indexer:reindex catalog_product_price

Expected result (*)

1. Product price reindex takes 1+ hours or more to complete.

Actual result (*)

1. Product price reindex takes a short time (2-3 minutes) to complete.

---

If we disable bundle products and perform price index then it completed within only 3 minutes but with enabled bundle products, it will take around 1+ hr.

We also tried to set higher values on some MySQL variables (i.e tmp_table_size,max_heap_table_size,innodb_buffer_pool_size) as per standard guideline as per below link but its not help us.
https://devdocs.magento.com/guides/v2.4/install-gde/prereq/mysql.html

We also done some more investigation for this issue and found one Insert query (attached screenshot) which is taking too long while price reindex running.

Look like same issue as per below patch but here we have magento community edition + 2.4 versions
https://support.magento.com/hc/en-us/articles/360051183691-MDVA-31224-Magento-patch-Product-price-reindex-takes-too-long

Please note: Above same configuration + if we use MySQL 5.7 then price index working fine without any extra time and completed within only 5 mins.

[m2-assistant]

Hi @davidandersson1. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[romainruaud]

@davidandersson1 I do have the exact same issue with MariaDB 10.1 (I don't want to update on latest since there are other known issues with recent MariaDB).

[romainruaud]

That being said it appears that the MDVA-31224 patch is available here : https://github.com/magento/quality-patches/blob/master/patches/os/MDVA-31224__improves_performance_of_catalog_product_price_reindex_operation_for_bundle_products__2.3.3.patch

I'll have a look at it to see if this improves things for me.

Regards

[romainruaud]

Okay, after a quick test :

• patch MDVA has no effect, it's already what is included in Magento 2.4.1

However as stated in #29264 I switched these lines :

$query = $select->insertFromSelect($this->getBundleSelectionTable());
//$query = $select->crossUpdateFromSelect($this->getBundleSelectionTable());

And the index did run in 2 minutes instead of hanging forever. Prices in the index table seems to be accurate.

Maybe you could give this a try on your project also. I'm curious if that does also fix your situation.

Regards

[davidandersson1]

Hi @romainruaud, Thanks for your help! I have checked with switches lines as you mentioned above but somehow its not help.

And yes, you are right that MDVA-31224 patch is already included in Magento 2.4.1

However, as per my previous investigation, method calculateDynamicBundleSelectionPrice (line no 588 in vendor/magento/module-bundle/Model/ResourceModel/Indexer/Price.php file + Magento version 2.4.1) tooks too longs to finish that's why price index time much increased instead of normal time to complete.

Please help us if anybody faced issue and got some solution for the same.

Thanks in advance,
David Andersson

[davidandersson1]

Hello,

May I know, is there any update for us?

We are really eager to resolve this issue and at this time we have no possibility to upgrade the latest version on production server without resolve this index issue.

I request you to all, If anybody faced same kind of index issue and found any solution for same than please share with us.

Thanks in advance,
David Andersson

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

[davidandersson1]

Hello,

Is there any update for us? really waiting from long time to resolve the issue!

Anybody please help!

[cdekkers]

Just noticed this problem in our similar setup. Price index takes way too long to complete. With ~130k products, the process takes about a minute for Magento 2.3, and around 2 to 3 hours on Magento 2.4.

[m2-assistant]

Hi @engcom-Alfa. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.