Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Performance issue - sporadic spikes in response times



Users of the application are facing sporadic / intermittent spikes in response times

Error Messages


Steps to Reproduce


Root Cause

From analysis of the PegaRULES-ALERT log files from multiple days and multiple nodes from production the external webservices calls (Rule-Connect-SOAP) calls clearly indicate as the root cause of the performance bottleneck. Also the PegaRULES log files indicate issues arising out of
SocketTimeoutException(s) on SOAP Webservices calls and the large numbers of TCP ports on “CLOSE_WAIT”


The following recommendation have been provided to alleviate this issue –
  1. HFix-6894 - options to set apache http connection pool size for R-C-SOAP
  2. A list of identified external webservices whose response times / performance SLA needs to be optimized.
Database table Indices recommendations –
Pega DBAs recommend adding the following indexes to Pega ‘queue’ tables to optimize performance of SPPR_SYS_RESERVEQUEUEITEM_B in production.
create index queue_reserve on pr_sys_queues (pyMinimumDateTimeForProcessing ASC, pyItemStatus ASC);
create index queuesvc_reserve on pr_sys_queue_execreq_svc (pyMinimumDateTimeForProcessing ASC, pyItemStatus ASC);
create index queueconn_reserve on pr_sys_queue_execreq_conn (pyMinimumDateTimeForProcessing ASC, pyItemStatus ASC);
create index queuesla_update on pr_sys_queue_sla (pyItemId ASC, pyItemStatus ASC);      
create index queuesla_reserve on pr_sys_queue_sla (pyMinimumDateTimeForProcessing ASC, pyItemStatus ASC);

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community 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
Contact us