Question
EPAM Systems
CA
Last activity: 27 Sep 2018 5:07 EDT
My Cases tab is very slow
Hi Team,
In our application we are noticing that My cases tab is very slow and after my research I find out in ootb rules we are not using Pagination and its trying to load all cases related to user.I tried setting pagination in section but still fetching all records from DB through Activity.
pyReportName=pyMyCasesReport;*Database operation took more than the threshold of 500 ms: 2,301 ms
Any suggestion to resolve this ?
Thanks,
Lalit
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
FR
Hello Lalit,
Which Pega version are you running?
EPAM Systems
CA
Pega PRPC 7.1.5
Pegasystems Inc.
FR
All right,
Have you tried to check with your DBA why this query is too long and if anything could be done at database level.
-
Lidia Zamarron
EPAM Systems
CA
Yea I checked and we have applied the appropriate indexes as well. Looks like activity is pulling too many request at one go and we need to apply Pagination. I checked in 7.3 and 7.4 also we don't have the pagination. If user is having 1000 records it, it will try to pull all records and display.
Pegasystems Inc.
FR
On my system the max number of records is set to 500 on this report. Anyway nothing is FINAL here you can change the report yourself right.
EPAM Systems
CA
Thanks for the reply!!
I checked and found out we have also 500 records in report but not sure why we are getting too much slowness in prod and I have noticed this in DEV as well. Below is the snap from Prod Alerts logs.
Thanks for the reply!!
I checked and found out we have also 500 records in report but not sure why we are getting too much slowness in prod and I have noticed this in DEV as well. Below is the snap from Prod Alerts logs.
8*TABTHREAD0*com.pega.pegarules.data.internal.access.DatabasePreparedStatementImpl*pegauswm.fg.com| Proprietary information hidden*[email protected]*Rule-Obj-Activity:ApplicationSetup*RULE-OBJ-REPORT-DEFINITION PXRETRIEVEREPORTDATA #20140423T091233.014 GMT Step: 24 Circum: 0**pxRDBIOCount=2;pxLegacyRuleAPIUsedCount=1;pxDeclarativeRulesInvokedElapsed=0.00;pxOtherCount=9;pxInteractions=1;pxRuleCount=6;pxRunStreamCount=5;pxOtherIOElapsed=0.06;pxTotalReqTime=32.82;pxRuleIOElapsed=0.02;pxRunWhenCount=38;pxDeclarativeRulesInvokedCount=5;pxActivityCount=26;pxProceduralRuleReadCount=4;pxOtherIOCount=5;pxTrackedPropertyChangesCount=45;pxTotalReqCPU=0.07;pxDBInputBytes=139,683;pxInputBytes=288;pxRunModelCount=5;pxRulesUsed=869;pxRDBIOElapsed=32.47;pxAlertCount=1;pxRuleFromCacheCount=4;pxRulesExecuted=22;pxOtherFromCacheCount=8;*Rule-Obj-Report-Definition*NA*Embed-ReportContent*NA*doActivity Rule-Obj-Report-Definition;Java;RULE-OBJ-ACTIVITY RULE-OBJ-REPORT-DEFINITION PXRETRIEVEREPORTDATA #20140423T091233.014 GMT Step: 24 Circum: 0;doActivity Rule-Obj-Activity:pxRetrieveReportData;Java;20 additional frames in stack;*pyPageName=treePagetemp;IgnoreObjCreation=true;CopyAlways=true;pyReportName=pyMyCasesReport;pyReportClass=ABC-xyz-pqr-Work;pyRunType=FullResolve;*Database operation took more than the threshold of 500 ms: 32,429 ms SQL: SELECT "PC0".PYLABEL AS "pyLabel", "PC0".PYID AS "pyID", "PC0".PYSTATUSWORK AS "pyStatusWork", "PC0".PXCOVERINSKEY AS "pxCoverInsKey", "WP".PYPARTYIDENTIFIER AS "pyPartyIdentifier", "WP".PYPARTYFULLNAME AS "pyPartyFullName", "PC0".PYSLAGOAL AS "pySLAGoal", "PC0".PXURGENCYWORK AS "pxUrgencyWork", "PC0".PXOBJCLASS AS "pxObjClass", "PC0".PYSLADEADLINE AS "pySLADeadline", "PC0".PYCUSTOMERNAME AS "pyCustomerName", "PC0".PXCREATEDATETIME AS "pxCreateDateTime", "PC0".PXCOVEREDCOUNT AS "pxCoveredCount", "WP".PXPARTYROLE AS "pxPartyRole", "WP".PYPARTYFULLNAME AS "pyPartyFullName", "PC0".PZINSKEY AS "pzInsKey" FROM VLM0.PC_Work "PC0" INNER JOIN RXRF.pc_index_workparty "WP" ON (( ( ("PC0".PZINSKEY = "WP".PXINSINDEXEDKEY) ) AND ("PC0".PXOBJCLASS LIKE ?) AND ("WP".PXOBJCLASS = ?) ) ) WHERE ( ("PC0".PXCOVERINSKEY IS NULL ) AND ("PC0".PYSTATUSWORK NOT LIKE ?) AND ("WP".PYPARTYIDENTIFIER = ?) ) AND ("WP".PXINDEXPURPOSE = ?) ORDER BY 8 DESC, 10 ASC, 12 DESC*
Pegasystems Inc.
FR
All right,
So only 500 records back. Can you get the query and ask your DBA to run it directly on the database side. It will be easiest to understand why the response is too slow.