Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Varvara Guseva (VGuseva) CustomerTimes Pega Certified Senior System Architect
CustomerTimes
CY
VGuseva Member since 2014 4 posts
CustomerTimes
Posted: Dec 14, 2015
Last activity: May 21, 2022
Posted: 14 Dec 2015 6:51 EST
Last activity: 21 May 2022 13:00 EDT
Closed
Solved

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.

To see attachments, please log in.
Pega Customer Service Data Integration System Administration

Posted: 8 years ago
Updated: 8 years ago
Posted: 14 Dec 2015 7:02 EST
Updated: 14 Dec 2015 7:04 EST
Rajiv Nistala (nistr) Senior Manager - Engineering
Pegasystems
IN

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

To see attachments, please log in.
Posted: 8 years ago
Posted: 14 Dec 2015 10:10 EST
Varvara Guseva (VGuseva) CustomerTimes Pega Certified Senior System Architect
CustomerTimes
CY

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.

To see attachments, please log in.
Posted: 8 years ago
Posted: 15 Dec 2015 6:24 EST
Rajiv Nistala (nistr) Senior Manager - Engineering
Pegasystems
IN

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

To see attachments, please log in.
Posted: 8 years ago
Posted: 14 Jan 2016 2:50 EST
Varvara Guseva (VGuseva) CustomerTimes Pega Certified Senior System Architect
CustomerTimes
CY

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.

To see attachments, please log in.
Posted: 8 years ago
Posted: 14 Jan 2016 3:23 EST
Rajiv Nistala (nistr) Senior Manager - Engineering
Pegasystems
IN

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

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice