You are viewing limited content. For full access, please sign in.

Question

Question

Search and performance

asked on March 13, 2013 Show version history

Is it possible to prevent a user from performing a "heavy search" for instance, a fuzzy Word search of "a"?

For instance, is it posible to set up a mínimum quantity of characters or force search text to be combined with a field search. If the system becoms unresponsive or with a very poor performance, is it posible to figure out which user/session is performing the "heavy search" to kill the session and free the server?

 
1 0

Answer

APPROVED ANSWER
replied on June 26, 2013 Show version history

There’s currently no way to restrict users on the types of searches they can do. It’s mainly a training across the Laserfiche users on how they can most efficiently create a search and get the results they need.

 

If you need to find out who’s running these types of searches when the system seems to have come to a crawl, you have two choices. First, you can use the administration console and look at the current actions node. This node displays the current activities going on in the Laserfiche system but it most often displays long actions, such as searches and exports of large documents. It does not take into account a user having a document open. The second choice is using Windows Performance Monitoring (Using MS Performance Monitor) and setting up the Laserfiche counters.

 

 


 

0 0

Replies

replied on November 3, 2013

If the user has access to weblink then they may have restricted search options there.

 

Also, I believe that the next version of Web Access/LF Server is supposed to have some technology improvements to allow for quick retrieval of documents and help searches over Web Access have better performance. 

 

I believe there are some settings as well that you can enable to allow the search to perform quicker. Bypass browse and Bypass Filter Expressions would potentially offer performance enhancements. If you are not making use of filter expressions in the repository, there is no reason not to not turn on the bypass filter expressions privilege. No use adding overhead with a feature you dont make use of. 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.