Question

Searches take a long time

Search and Retrieval

Updated August 14, 2015

asked on July 17, 2015 • Show version history

After i migrate my client LF Server from 8.3 to 9.2.1 now all the searching its taking to loong.

They got LF Server with only 4GB of RAM and now we are like for 16 GB or RAM but because of the searching is taking that long slowly the perfomance during the day is consumed.

I got to admint they do search with 100,000 results. But if they make the same search by Web Access 9.2 what it takes like 30 minutes in Client now takes 3 minutes in WA.

Any ideas.

0 0

Answer

SELECTED ANSWER

replied on July 20, 2015

The advanced search syntax for "Document" type searches are slightly different in the Client and Web Access. The Client uses {LF:Name="*", type="DB"} while Web Access uses {LF:Name="*", Type="D"}. There's no difference in the search results returned by these searches, however, the Client's search causes a different SQL query to be generated that can add a delay to the search processing.

It was confirmed that when using the Client's advanced search, and changing the syntax manually to use {LF:Name="*", Type="D"}, the search ran faster.

One suggestion was to make sure that an index existed for the toc.pset_id column in the database.
If there's still an issue, then perhaps the issue can be worked around with a custom quick search.

In any case, this issue in general is something we're investigating. Workarounds can be used in the meantime.

0 0

Replies

replied on July 17, 2015

You could try reindexing the whole repository, I've seen that cut search times down quite a bit:

0 0

replied on July 17, 2015

I already do that and also delete them and re-create them.

Do nothing to the search performance.

0 0

View 1 previous reply

replied on July 17, 2015

What types of searches are being run exactly? If you can provide the full advanced search syntax, that'd be helpful. Are access rights a factor? If you search with an administrative user that has full rights and privileges, is there an issue?

There are many factors that come into play so it may be better if you opened a support case and provided full details regarding the types of searches being run, the users performing these searches, what search result columns are displayed, server specs of LFS, LFFTS, SQL, etc.

0 0

replied on July 17, 2015 • Show version history

Any user got the issue.

Take for example. If I use the admin (superuser) make the search in client takes 30 minutes or never ends. Use the WA and takes 3 to 4 minutes to retrieve 100,000 results.

The type of serch is thi type:

In folder (include subfolder)

only documents

Created this month

With the template "Template Name" (No field capture)

0 0

replied on July 17, 2015

The case you are referring to did not contain the information you mentioned in this Answers thread. The case contained various metrics regarding how much RAM and CPU was being used, how many active sessions existed concurrently, how much Workflow processing, Import Agent processing, etc was being done at the time, etc.

If the other aspects can be filtered out and you are able to just troubleshoot the singular issue with searches running slower since the upgrade, and you can demonstrate that it's in particular the searches being done from the Client being slow with the same search in Web Access being faster, then we can better troubleshoot the issue.

Please update the case with the requested information that's relevant to troubleshooting this search issue (actual search being run - advanced search syntax, search result columns displayed, details comparing how the searches are being run in Web Access vs the Client and by who, etc) and we can look into the matter further.

0 0

SELECTED ANSWER

replied on July 20, 2015

It was confirmed that when using the Client's advanced search, and changing the syntax manually to use {LF:Name="*", Type="D"}, the search ran faster.

One suggestion was to make sure that an index existed for the toc.pset_id column in the database.
If there's still an issue, then perhaps the issue can be worked around with a custom quick search.

In any case, this issue in general is something we're investigating. Workarounds can be used in the meantime.

0 0

You are not allowed to follow up in this post.

Question

Question

Searches take a long time

Answer

Replies

Sign in to reply to this post.