You notice poor performance in the Web Client in showing the results list page.
This could be due to a number of different reasons: debug logging enabled, expensive search query, slow Web Client sorting, slow database connection, Microsoft Internet Information Services overload, and more.
The purpose of this article is to provide a troubleshooting step by step guide and rule out simple possible causes.
Expensive search query:
Try searching for a specific word, with no special characters like star (*) or question marks (?). If this results in the results page being shown in a timely manner, and the poor performance is only observed when using special characters, it could be that the search query is expensive for the index to resolve.
Debug logging enabled:
Debug logging level being enabled will negatively affect the performance. To rule this out, you can easily turn logging level back to INFO by following the steps suggested in the "How to set logging for the Information Management Platform" knowledge base article.
Slow Web Client sorting:
If the issue is with post-processing the results list in the Web Client, you can try changing the sorting method from the drop-down menu (right below the search box) to "Last indexed first". This way no sorting will be applied and the results pages will just be populated as results come.
Slow database connection:
If you are searching on a field value, and the field is a database field, it could be that access to the database is slow. Contact your Database Administrator and ask to confirm how long it takes for the database to return values for the same query.
Microsoft Internet Information Services (IIS) overload:
If you are the Microsoft IIS Administrator, you can check the health and logging settings of the different modules in IIS. Also you can monitor the hardware performance of the machine to make sure that is not a constriction.
6.2; 6.2 Service Pack 1; 6.2 Service Pack 2; 6.3; 6.4
Article is closed for comments.