Friday, April 1, 2011

PAL Reports

Performance Tool is sometimes called as PAL. To understand the system resources consumed by processing of a single requestor session or the sql statements sent to the Pega DB by the requestor session.

Using PAL we can assess the possible sources to improve the performance through rule changes, s/w changes/ hardware changes.

The DB Trace facility logs all SQL interactions between your Process Commander session and the PegaRULES database.

Runà Performance or type CTRL+Q

We have DB trace Option link to track DB events like Prepared Statement Queries/updates, Read BLOB/Write BLOB, commit, rollback, Cache hits, cache miss, activity start/end etc.

2 comments:

  1. Can you please answer this question ?

    Before running PAL , you should make sure to run the functionality atleast once to ensure rule assembly is done or else it effecs performance reading for that functionality..

    Thankyou...

    ReplyDelete