Following are the different ways by which we can measure the performance of our application in Pega :
DBTrace : The Performance Analysis Tool (PAL) has a feature called DBrace that provides a thorough log of calls to the PegaRULES database. DBTrace shows the time spent on each operation as well as the SQL queries delivered to the database.
Performance Analyzer Tool : The Performance Analyzer (PAL) displays all of the performance statistics collected by Pega PlatformTM. You can utilise PAL to figure out how much system resources a single requestor session uses. The Performance landing page (Dev Studio > System > Performance) and the Performance tool in the toolbar both have PAL.
The features of PAL includes the following :
* To add reading
* To add reading with clipboard size
* To reset data
* To save data
* To configure DBTrace options
* To start profiler
* To show alerts
Alerts : Process Commander inserts a succession of text entries called alert messages to the performance alert log during application execution to identify mostly performance-related issues or faults. PegaRULES-ALERT-YYYY-MMM-DD is the most common name for the performance alert log.
Autonomic Event Services (AES) : Exceptions are handled in the same way that alerts are. Exceptions generated by a Process Commander server are sent to the AES system via SOAP. The system parses the exceptions and registers them in the AES database's pegaam exception table. AES aggregates these records into work objects called AES exception items based on how frequently an exception occurs and the system events that produced those exceptions. The pegaam exception work table in the AES database is used to store these objects.
