Virtual Happy Hour this month, Jun 28, we'll be getting a sneak preview at our soon to launch SaaS CMS!

Try our conversational search powered by Generative AI!

catalog indexing speed



We have an index of about 500,000 items, when clearing the index and running the find indexing job, the CMS indexes in less than an hour, but it takes 3-5 days to finish indexing the catalog (which has about 80% of the index size due to the large number of languages we have).

Does anyone have any tips on how to make the site index faster?

Part of the reason this is an issue is because so many find events dont reach the index (intermittent publishes/deletes/new content items) so over the cource of a few months, the index becomes less actual.



<>package id="EPiServer.Find" version="12.5.3" targetFramework="net46" />
<>package id="EPiServer.Find.Cms" version="12.5.3" targetFramework="net46" />
<>package id="EPiServer.Find.Commerce" version="10.0.0" targetFramework="net46" />
<>package id="EPiServer.Find.Framework" version="12.5.3" targetFramework="net46" />
<>package id="EPiServer.CMS" version="10.10.3" targetFramework="net46" />
<>package id="EPiServer.Commerce" version="11.2.3" targetFramework="net46" />
Oct 15, 2018 10:44

How many languages do you have - because each and every language content will need to be index? We know about the problem with big catalogs and have been taking some actions to make it better, but of course for very big catalogs it will still take time 

Oct 15, 2018 11:29

we have 115 languages enabled right now (though we are hitting some sql issues with activating more than 100 in Commerce).

Oct 15, 2018 13:00

Interesting. There should be no problem with activating more than 100 languages in Commerce. If you can share more information regarding that issue, I can look into it.

Oct 15, 2018 13:01

I have an open support ticket, in there i have detailed the issue, please take a lok if you get a chance, its an interesting issue

Oct 15, 2018 17:37

What is theticket number :)

Oct 15, 2018 17:41

Ofcourse! Its #204490

Oct 15, 2018 18:30

I see. So the problem was because one of our udtt(s) has Languages field which is NVARCHAR(512). Given that you have more than 100 languages and each might be in form of en-US which takes 5 bytes, so that means from the 103th languages the problem will appear.

The fix is quite obvious but it will require a newer version - the best I can is 12.11 or so. The only question is which version you are on and if you are willing to upgrade :) 

Oct 15, 2018 19:21

Normally the support team will escalate the ticket and create a bug, but given that I am already in the contact with you I will create one myself to shorten waiting time 

Oct 15, 2018 19:22

That would be great, thank you :), we are Ofcourse willing and able to upgrade. We are on 11.2 now but have an internal PR to upgrade to the latest version now.

Do you have an estimated release date for 12.11?

Oct 15, 2018 19:45

We are working on 12.10 right now, which might be finished at the end of this week (probably, who know for sure :) ). 12.11 (or 12.10.1 :) ) will take 1-2 weeks after that. So let's just say it will be released in November :) 

Oct 15, 2018 19:48

Going back to the issue about slow indexing through, Commerce content takes so very much longer to index than CMS content, ofcourse that could be the languages as well, is there anything in the works that could help with that?

Oct 18, 2018 9:18

Each and every language needs to be indexed, so given you have 500.000 contents and 100 languages each, it would be 50.000.000 contents to index. I know Find 13.0.4 has some improvement on index queue and Find team is working on some improvements - but I don't know the detail. 

Oct 18, 2018 9:24
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.