Question
Can execution time of lucene query be improved? Can I determine effectiveness of search request?
Can execution time of lucene query be improved? and how can it be improved?
Can I determine effectiveness of search request? And how?
At the project there is searching for a work object by lucene indexes. The execution query time is too long time.
The data about too long execution time was taken from pega alerts.
PRPC: 6.1 SP2.
Query runs from the doSearch function. Function received a generated query from activity.
The generated search query contains parameters to search work objects. All parameters, that used at the query, have search indexes.
Hi Varvara,
Would it be possible to share the parameter values to this function?
Also, would it be possible to use the pySearchResultsWork List View instead?
-Rajiv
Hi Rajiv,
Rajiv Nistala wrote:
Hi Varvara,
Would it be possible to share the parameter values to this function?
Also, would it be possible to use the pySearchResultsWork List View instead?
-Rajiv
Sharing parameter to this function does not needed at first sight at it. Because doSearch function(activity) only sends soap request to ConnectRuleSearch (standard connect soap ), request is handled and than results are passed.
pySearchResultsWork List View can not be used instead because there are used specific data for searching and there are showed specific data.
Hi Varvara,
There are some generic options that Lucene recommends for query execution. The first one is not to use a prefix wildcard. The second is to filter results based on targeted fields. But all of these are also a function of the size of the index what the search string is (how generic it is).
How slow is the query right now? There have been improvements in newer versions of Pega platform through the upgrade of Lucene library in 6.3 and to Elastic Search in 7.1.7. They have definitely improved the performance of full text search in the Pega platform.
Also, you might want to install HFIX-5451 to reduce the memory footprint of Lucene in 6.1 SP2.
-Rajiv
Also, with ElasticSearch we have a new alert for search queries taking longer than a threshold - https://pdn.pega.com/understanding-pega0054-alert-query-exceeded-operation-time-threshold-0
Hi Varvara,
Please share which version of the pega platform you are using.
Also, share the details of how you are executing the Lucene query. Is it via the FindWork gadget or through the Search control in designer studio?
-Rajiv