Tracking rule utilization for a requestor session with Performance Profiler
Use the Performance Profiler landing page to obtain a detailed trace of performance information about the execution of activities, when condition rules, and data transforms executed by your requestor session. The Profiler traces every execution (in all threads) of rules of these three types in all rulesets, and creates a separate output file for each thread in your session.
On UNIX-based servers, only elapsed time statistics are available; CPU statistics are not available.
Use this tab to obtain a detailed trace of performance information about the execution of activities, when condition rules, and data transforms executed by your requestor session. The Profiler traces every execution (in all threads) of rules of these three types in all rulesets. Trace records are saved as instances of the Log-Trace-Profiler class.
- Profiling your requestor session
Use the Performance Profiler to profile rule usage for your requestor session. By profiling your session, you can readily associate user actions with profile results.
- Interpreting Performance Profiler results
Interpret the results of Performance Profiler so that you can identify what changes might improve system performance.
- Profiling all processing on a node
You typically use the Performance Profiler to profile rule usage of one requestor, but you can also profile all activity for a node to get an overall picture of system usage.
- Profiling another requestor
To enable the Performance Profiler to see rule usage for any requestor on any node, use the Admin Studio Requestor Management tool to start profiling. For more information, see .
Previous topic Viewing statistics for services in the SERVICES-PAL log Next topic Profiling your requestor session