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

Using Elasticsearch in Backend / Product Filtering with 3.000.000 Products #579

Open
phpsyscoder opened this issue Oct 20, 2017 · 4 comments

Comments

@phpsyscoder
Copy link

phpsyscoder commented Oct 20, 2017

Dear Team (its a "Question-only-Issue" )

we using Mage2 with 3.000.000 Products... Elasticsearch did a great job... very fast.

But the Build-in Backend Seach/Filtering for the Products is - of course - very slow, our customer have to wait up to some minutes for ie filtering by "Product Name".

Is it possible to use the Elasticsearch-Engine for the Backend-Product Search also?

Any Help/Tips are welcome

Greetings
Hans-Jürgen Petrich

@romainruaud
Copy link
Collaborator

@Petrich thank you for submitting this request.

This is something we also noticed by our side, on a project of a similar size as yours.

It would seem quite easy to plug Elasticsearch for product grids in Backend at first sight, but there are some issues :

  • some fields are coming from SQL joins (Eg the "qty" field).

  • not all products are indexed into Elasticsearch : simple products are not, which would make them disappear from the grid

We were thinking about having a second index dedicated to the grid but this causes quite a duplication of data between the "search" and the "grid" index.

But this is a point we definitely plan to address.

Best regards

@southerncomputer
Copy link
Contributor

southerncomputer commented Oct 23, 2017

How about using shared Catalog theory to make a ZERO group ID filter for backend and ONE group ID for default front-end to import all products?

@Petrich - you must modify grid collection search to use index not like '%'+term+'%' with wildcard on both sides to not use full table scan!

@Nuranto
Copy link
Contributor

Nuranto commented Nov 16, 2022

I guess a partial implementation, on fulltext search only (which is the slowest, with that union all sql query), could already help a lot.

@Mobecls
Copy link

Mobecls commented May 15, 2023

Dear Team (its a "Question-only-Issue" )

we using Mage2 with 3.000.000 Products... Elasticsearch did a great job... very fast.

But the Build-in Backend Seach/Filtering for the Products is - of course - very slow, our customer have to wait up to some minutes for ie filtering by "Product Name".

Is it possible to use the Elasticsearch-Engine for the Backend-Product Search also?

Any Help/Tips are welcome

Greetings Hans-Jürgen Petrich

And how many attributes and filters do you have?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants