I've got a fairly hefty Examine index setup in ExamineSettings.config - which normally has 400 fields with around 10000 entries at a time - as follows:
which is using a simple data indexer with GetAllData to take values from a SQL query and push them into my Examine index. When a user uploads a CSV (which is fairly large - around 7000 rows of data), this data is first written to SQL, then the IndexAll action is called afterward:
var indexer = ExamineManager.Instance.IndexProviderCollection[IndexConstants.ExternalTestIndexer];
indexer.IndexAll(IndexConstants.ExternalTestIndexType);
At this point, the index is repopulated correctly. However, afterwards the site becomes very slow, with page response times taking up to 1/2 minutes. There's no hardware bottlenecks, and eDTU usage in Azure hovers around 40%. Have done all instructions posted here and I'm still seeing this issue - is it due to the size of the index potentially? Or something else I'm missing? Thanks.
Azure Examine Index
I've got a fairly hefty Examine index setup in ExamineSettings.config - which normally has 400 fields with around 10000 entries at a time - as follows:
which is using a simple data indexer with GetAllData to take values from a SQL query and push them into my Examine index. When a user uploads a CSV (which is fairly large - around 7000 rows of data), this data is first written to SQL, then the IndexAll action is called afterward:
At this point, the index is repopulated correctly. However, afterwards the site becomes very slow, with page response times taking up to 1/2 minutes. There's no hardware bottlenecks, and eDTU usage in Azure hovers around 40%. Have done all instructions posted here and I'm still seeing this issue - is it due to the size of the index potentially? Or something else I'm missing? Thanks.
How often do users upload csvs basically how often is the indexing triggered?
Hi Ismail, thanks for replying.
The plan is currently for the CSV to uploaded every 2-3 days
is working on a reply...