FAQ Magento How many records does the Magento extension create?

Last updated 12 April 2017

The Magento extensions creates several indices.

To be able to have very fast results Algolia precomputes part of the order of the results at indexing time. This means that you cannot have multiple sorts for a single index. To handle multiple sorts, we need to create 1 Algolia index for each sort.

In Magento, this results in creating by default:

  • 1 index per store
  • 1 index per store per additional sort order (by price, by date, …)

Which means that for a Magento instance with:

  • 2 stores (2 languages for example)
  • 100 products
  • 2 sorts on “price” (asc, desc)
  • 2 sorts on “date” (asc, desc)

You’ll have 100 * 2 + 100 * 4 * 2 = 1000 Algolia records.

-—-

If you enable the customer group feature it creates :

  • 1 index per store
  • 1 index per price sort per group per store => This is to be able to have the correct sort on price no matter what the user group
  • 1 index per non-price sort per store

Which means that for a Magento instance with:

  • 2 stores (2 languages for example)
  • 100 products
  • 5 customer groups
  • 2 sorts on “price” (asc, desc)
  • 2 sorts on “date” (asc, desc)

You’ll have 100 * 2 + 100 * 2 * 5 * 2 + 100 * 2 * 2 = 2600 Algolia records.

-—

You can reduce the number of records by removing some sorts. This can be configured in the extension administration panel. See the screenshot below.

Did you find this page helpful?

We're always looking for advice to help improve our documentation! Please let us know what's working (or what's not!) - we're constantly iterating thanks to the feedback we receive.

Send us your suggestions!