OOTB functionality causing performance issues
PEGA0005 alerts when sppr_purge_table (?,?,?) is being called. Even though user reduced the retention period for ‘pr_perf_stats’ table to 7 days from 30 days, they are facing the same performance issue and alerts are generating daily.
Steps to Reproduce
A software use or operation error, ‘pr_perf_stats’ table contains PAL data for every requestor on every node connected to that rulebase. More details can be found here https://pdn.pega.com/sites/default/files/help_v719/procomhelpmain.htm#howto/howto2/logusagetable.htm along with how to change retention days.
There will be a lot of data in this table and this could impact performance if you use the reports that go against this table or the nodes that are being monitored by AES or PDC.
If there is a lot of data in ‘pr_perf_stats’ table you can try truncating this table in your downtime. You have set the retention period to 7 days from 30 days, so ‘System cleaner will run and purge the records older than 7 days. Reducing the retention period will overload the stored procedure as it has nearly all entries to delete from the table and as obvious stored procedure exceeds the threshold.
Keep the default value as 30 days (or) the System cleaner can be made to run periodically every 30 minutes to purge the records older than 7 days or 30 days.
The daily alerts are expected since each day the Pega-RULES agent starts a stored procedure that purges older rows of this table, passing the value of the pxProcess property as the number of days to retain. In this case the stored procedure will be run daily to purge records older than 7 days.
General performance recommendations including pr_perf_stats are mentioned here - https://pdn.pega.com/performance/performance-guidance-for-production-applications-database
0% found this useful