Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Issue] Remove unnecessary clause from price index queries #32382

Closed
2 of 4 tasks
m2-assistant bot opened this issue Mar 4, 2021 · 6 comments
Closed
2 of 4 tasks

[Issue] Remove unnecessary clause from price index queries #32382

m2-assistant bot opened this issue Mar 4, 2021 · 6 comments
Labels
Area: Catalog Component: Catalog Component: Indexer Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: needs update Additional information is require, waiting for response Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: done Reported on 2.4.x Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch

Comments

@m2-assistant
Copy link

m2-assistant bot commented Mar 4, 2021

This issue is automatically created based on existing pull request: #32223: Remove unnecessary clause from price index queries


Description (*)

This removes a line that was rendered unnecesary by #22575. Currently there are two filters in the where clause for entity ID's. Since the second one explicitly lists the individual entity ID's, the BETWEEN AND clause is redundant. In testing on mariadb 10.2 and 10.3, removing the BETWEEN AND clause yields significant improvements in catalog price indexer performance on stores with large catalogs.

Related Pull Requests

Fixed Issues (if relevant)

Manual testing scenarios (*)

  1. Run catalog_product_price reindex on store with a large catalog of products.
  2. Remove or comment out the line that this pull request removes.
  3. Run reindex again and compare speed to first run.

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)
@m2-assistant m2-assistant bot added Component: Catalog Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. labels Mar 4, 2021
@engcom-November
Copy link
Contributor

Verified the behavior on Magento 2.4-develop instance with 10k products and Product price reindex took 01 sec but where as Catalog Search index took 18 seconds to reindex.
image

@engcom-November engcom-November self-assigned this Nov 8, 2022
@m2-assistant
Copy link
Author

m2-assistant bot commented Nov 8, 2022

Hi @engcom-November. 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).

    DetailsIf 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.

@engcom-November
Copy link
Contributor

Verified the behavior again on Magento 2.4-develop instance with 19k products (With both simple and configurable products combined) and Product Price index took 00:06:25 time during reindex.
image

@engcom-November
Copy link
Contributor

Verified the issue again on Magento 2.4-develop instance with and without PR changes. On an instance with 20k products - Product Price index took 00:06:25 time during reindex. After removing / commenting the line mentioned in PR , Product Price index took 05 seconds during reindex on an instance with 40,000 products. Hence confirming this issue.
image

@engcom-November engcom-November added Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Component: Indexer Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Reported on 2.4.x Indicates original Magento version for the Issue report. Area: Catalog labels Nov 9, 2022
@github-jira-sync-bot
Copy link

✅ Jira issue https://jira.corp.adobe.com/browse/AC-6996 is successfully created for this GitHub issue.

@m2-assistant
Copy link
Author

m2-assistant bot commented Nov 9, 2022

✅ Confirmed by @engcom-November. Thank you for verifying the issue.
Issue Available: @engcom-November, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Catalog Component: Catalog Component: Indexer Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: needs update Additional information is require, waiting for response Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: done Reported on 2.4.x Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch
Projects
Development

Successfully merging a pull request may close this issue.

2 participants