How to discover most frequently executed RA rules Rules assembly involves generating and compiling Java code corresponding

to a rule at the moment that the Java code is first needed to execute, rather than in advance Process Commander generates rules-assembly Java for activities, stream rules, most decision and declarative rule types, parse rule types, and others. Click the Show Java toolbar button it appears to view an approximate preview of the run-time Java generated by the rules assembly facility V6.2SP2 includes a statistics-collection facility for those rule types that are assembled into Java When a node is shut down, these statistics are saved as instances of the LogRuleUsage class Starting with V5.3, these statistics are collected by the Pega-RULES agent (rather than at shutdown), which periodically runs the standard activity Code-.RuleUsageSnapshot (An agent is an internal background process operating on the server on a periodic basis) at system shutdown and once each 24 hours the system records statistics about the contents of the rules assembly cache in instances of the Log-RuleUsage and LogRuleUsage-Detail classes. This information is normally used at the next system startup to "prime" the rules assembly cache during the next system startup, so that it doesn't start empty By default, the rules assembly cache is limited to 20,000 entries. If this limit is approached during system operations, older entries are discarded automatically to make room for newer entries, following the Most Recently Used (MRU) algorithm This process increases startup time but can provide a performance benefit by avoiding the need to reassemble and recompile rules that are already assembled and compiled from earlier system sessions Log-RuleUsage Class Has 11 Properties. 1. pxClassName 2. pxFamilyName 3. pxLastUse 4. pxNumInvalidate 5. pxNumLoads 6. pxNumPeeks 7. pxNumReload 8. pxRuleCount 9. pxSize 10. pxSystemNode 11. pxUseCount

pxLastUse Date and time that the rule was last executed, as recorded in the rules assembly cache. pxNumPeeks Number of times the class loader checked to see whether this entry was loaded. pxNumInvalidate Number of times the cache content was invalidated (unloaded), such that the next request forces rules assembly. rules assembly pxNumLoads Number of times this class was loaded. pxNumReload Number of times this class was reloaded without forcing a rules assembly. pxRuleCount Number of dependences that this rule has. pxCreateDateTime First date and time this rule was captured by this snapshot. pxUpdateDateTIme Most recent date and time this rule was captured by this snapshot. pxSize Size of the Java CLASS file in bytes. pxSystemNodeNode ID (hash) on which this snapshot was captured.Node ID pxUseCount Number of times this rule was requested from the rules assembly cache. These Properties are mapped to PR4_LOG_RULE_USAGE Table in PegaRules Database. By default all the properties in the table is exposed to achieve the reporting fecility. pxAssemblyCacheKey pr4_log_rule_usage_details pxDetailIndex pxParentRuleUsageKey