Search Performance after adding a new field to template

asked on October 6, 2015 • Show version history

A week ago, I was requested to add another field to our main Income Tax Template. This template is the main template we use for our Primary Repository which holds 21 million documents. The new field is a date field using the Short Date format. I added the field over the weekend to let it apply without interrupting anyone during the work week.

Since I added this new field when our users perform searches using the Income Tax Template the searches are very slow and take a long time to respond. They do finally respond but we are talking 3-5 mins., which is much longer than before. The field they are searching on is an existing field and not the new field I have added as there is no data in this field as of yet. Is there something wrong causing this to slow down the performance?

I am currently Re-indexing the entire Repository which I started last Tuesday. I thought this might help the search performance. The indexing will not be finished for a few more days. We are only indexing field data and not using Full Text searches.

If the user does Field Searches on the fields they want to find, then the performance is fine. It is only when they use the Income Tax Template to search by that it is slow.

Any suggestions as to what is going on?

Thanks in advance!

Robin

0 0

replied on October 6, 2015

I've always wondered how a template search works versus a field search. I'm wondering if it's like this:

Field A: Blank <- pre existing field, filled in on 95% of docs

Field B: Blank <- pre existing field, filled in on 95% of docs

Field C: Search String <- pre existing field, filled in on 95% of docs

Field D: Blank <- New field, blank on all of them

so my thought on this is that before when you searched if you left most of the fields blank there were very few documents that matched those blank fields. But now there are three million documents that match D, and it's grabbing those documents first before searching through them to look for C.

I.e. if the documents have data it ignores that it is blank, but if blank actually matches then it does a comparison?

I'm not sure.....

0 0

replied on October 6, 2015

I added another field two weeks prior and never had this issue and that field is still blank as well.

We are going to be populating these through a script from our developers in the near future, but only on new documents not older existing ones.

0 0

Question

Question

Search Performance after adding a new field to template

Replies

Sign in to reply to this post.