How to use performance profiler controls in SMA?
How to use performance profiler controls in System Management Application (SMA)? And, where does the trace data (CSV formatted file) gets generated when user performs application performance profiling via SMA?
Profiling data (CSV file) get generated under prTemp - Application Profiler directory.
The Start Profiling and Stop Profiling buttons control the Performance Profiler, which produces a detailed trace of activity, when condition, model, and stream rule execution. The Performance Profiler traces every execution in all threads of rules of these types in all RuleSets. This is the same tool that is accessed through the Pega button’s System > Performance > Performance Profiler menu in the developer portal. To start the Profiler from the Requestor Manager:
1. Click Start Profiling to initialize the data collector for the selected requestor and begin data collection to a trace log.
2. Run the activities or other rules to be profiled.
3. Click Stop Profiling.
4. Save trace data to a CSV-formatted file in the PegaRULES temporary directory. Files are named by the requestor identifier_thread name, for example: HCF9AC2433F6D7C1FECACEB1F5EE8A0F9_STANDARD.csv.
The Performance Profiler lists items in the order they were completed, and therefore rows might not be written to the trace file in the order the sequences were started. To see the steps in consecutive order for a given interaction, sort on the Sequence column for that interaction in the output table.
Refer SMA Reference Guide on PDN for more details.
66.666666666667% found this useful