-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Fulltext search index: slow query in resetSearchResults() #566
Comments
@arhu32, thank you for reporting this to us! We created a ticket in the backlog and will get back to you once the team investigates on this issue. |
hey @verklov , was this issue solved in CE 1.9? |
Hi @bachsh, I don't think it is solved in CE1.9 already. In any case, once we have a solution for M2, we will have it requested to be ported to M1 by the M1 team. |
Internal ticket: MAGETWO-24366 |
…rchResults() #566 - Fix static tests
@arhu32 The fix is now available in 0.74.0-beta10. Thank you very much for your contribution and continued support to Magento 2! Could you please verify the issue? |
[GoInc] Configurable Product Variation Update, manual selection product an association - create grid
[SUPPORT] MDVA-198: 2.0.5 backlog
Fixed issue: - Split Deployment - scrub sensitive data - override config values by environment
In Magento/CatalogSearch/Model/Resource/Fulltext.php, function resetSearchResults() there are some queries that set the whole column "is_processed" in the table "catalogsearch_query" to 0, e.g.:
This query is very slow because it possibly needs to update lots of rows every time resetSearchResults() is called. On our server (mage181, multi-store setup, no SSD) with ~40.000 rows in the table, the query took 0.5 seconds and was called regularly during product updates etc.
Fix:
Only update rows that are not already 0:
Add an index to the "is_processed" column in the "catalogsearch_query" table.
This will speed up the query considerably. AFAIK this issue affects all Magento versions, including 1.8.1.0.
The text was updated successfully, but these errors were encountered: