Performance issue: PEGA0037 and PEGA0001 occurrences observed
Multiple application developers in a Pega 7.1.7 environment report general performance problems and slowness.
No specific steps were isolated or identified as a cause for the performance issue; users logging into the environment after a restart immediately reported problems.
Steps to Reproduce
Analysis of the Pega ALERT log file indicated that database performance was significantly affecting the user experience. Examination of the SQL statements reported in the PEGA0005 alerts suggested that database performance was the root cause of the PEGA0037 alerts, leading to the long browser wait times (PEGA0001 alerts).
Additional analysis revealed that the standard report definition <DATA-RULE-SUMMARY>pzWarningsIntroduced (Pega-Desktop:07-10-13)was incurring a 400+ line SQL statement. This caused performance delays in excess of 10 seconds.
- Define additional INDEXes on the designated tables and properties. Details below.
- Isolate and disable the standard report defintion. Details below.
PROPERTIES: PZINSKEY, PYRULEAVAILABLE
PROPERTIES: PYHISTORYTYPE, PYWORKCLASS, PXOBJCLASS
PROPERTIES: PZINSKEY, PYID, PXOBJCLASS
To disable the standard report definition <DATA-RULE-SUMMARY>pzWarningsIntroduced (Pega-Desktop:07-10-13), complete the following steps:
- Save this section to the user's ruleset: <RULE-HTML-SECTION>@baseclass.RuleFormHeaderMessagesInner
- Update this newly saved section and remove the reference to the report definition <DATA-RULE-SUMMARY>pzWarningsIntroduced (Pega-Desktop:07-10-13).
- Save the updated section.
- Shut down Process Commander.
- For each PRPC node, delete the PegaRULES_Extract_Marker.txt file located in the PRPC Explicit Temp directory.
- Restart Process Commander.
0% found this useful