Hi,
I need some help/pointers so that I can investigate why an index of less than 40k products (log attached) with a very basic IndexBuilderExtender (code also attached) would take 10min to run.
Any pointers?
Best Regards,
Nuno Aguiar
Hi,
I need some help/pointers so that I can investigate why an index of less than 40k products (log attached) with a very basic IndexBuilderExtender (code also attached) would take 10min to run.
Any pointers?
Best Regards,
Nuno Aguiar
Cannot see what happens in your helper - but it looks innocent. Try to remove the extender and see.
How many field do you index? How many do you store?
BR Nicolai
Hi Nicolai,
I've worked with larger indexes and did not experience it. Maybe it's something in the data? But what? Any other ideas on how I can track this down?
Best Regards,
Nuno Aguiar
You can always attach a profiler during the indexing - see what methods it is.
It could simply be that you have many fields that is stored - causing a lot of IO and hence degration in performance.
Hi Nicolai,
>> You can always attach a profiler during the indexing - see what methods it is.
D'uh!!! Yes of course. I'll do that.
I'll let you know what I can find, especially if it's something we can improve in DW to make it better.
Best Regards,
Nuno Aguiar
Hi Nicolai,
This is still puzzling. A code profiler pointed to the index only (did not go through in detail), but we decided to look into a SQL Profiler and we found some interesting thing that need your help with.
https://www.screencast.com/t/jzc3VwWWL3by
I tried looking into the code for indexing, but I don't feel I know enough to get a clue.
Do you know of any reason why we'd be seeing this amount of time when requesting it through the Repository?
Best Regards,
Nuno Aguiar
Thoughts?
Hi Nuno,
I don't think the slowness is due to the SQL. Rather, I think that it's because of the amount of data that the builder needs to process. Since we don't release the DataReader until the records have been processed, you'll see it as a long-running query in SQL Profiler.
My recommendation would be to take a look at your builder settings and turn off unnecessary processing or minimizing the number of fields in order to bring the build time down. For example, you should turn on "SkipGroupSorting" and "SkipImages".
If this doesn't help, you may need to add a code profiler to see where the time goes. Alternatively, we would need a copy of the solution to investigate the issue.
- Jeppe
Hi Jeppe,
Thanks, I found out the issue, although I don't know if there's a solution for it. Maybe there's some optimization we can do in DW? I'll let you be the judge of that.
Best Regards,
Nuno Aguiar
You must be logged in to post in the forum