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.

Addressing a Connect Total Time performance alert (PEGA0020)

 This presentation is part of the Designing and Building for Performance Self-Study Course.



The Connect Total Time (PEGA0020) alert is triggered when a connector method call to an external system exceeds the system threshold of 1000ms.  Often times, a single request to PRPC may require multiple calls to connectors to external systems, and if these perform poorly, PRPC users are likely to experience long response times. 

Typically, the bottleneck is not due to PRPC but to the other application being accessed.  Bottlenecks can occur if the data being sent to or received from this connector is large and complex. 

Fixing these alerts often times require restructuring the design by:

  • Fixing the third party application to process the requests more efficiently
  • Reducing the payloads
  • Reducing the complexity of the data
  • Consolidating some of the connector calls to avoid network latency
  • Using more efficient connector types over others – for instance, MQ is more efficient than SOAP

This can take quite a bit of time to accomplish, so the earlier these issues are detected the better.

Did you find this content helpful?

Have a question? Get answers now.

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