The PROIV profiler is integrated into the PROIV Virtual Machine to provide seamless user experience. The PROIV profiler diagnosis CPU, memory usage or any other application-level issues and helps you to understand the overall performance of your application. You can identify the objects and also drill-down to the level of function calls that consumed a disproportionate amount of execution time. For example, if a single function takes up 80% of the execution time, it’s usually worth to identify bottlenecks and performance tuning opportunities in your application.

To setup the profiler, you must create a profiling session. During the profiling session the execution time for various PROIV objects is recorded and when the session ends, a trace file is generated in the specified path with a unique name with an extension of p4p. This trace file helps you to view the state of your application at different points during the execution of your code, such as:

• Function execution paths that were traversed by the objects

• Entry point of the component

• Time spent in the task (function time or self time) and in its descendent subprograms (subtree time)

• Detailed parent-children information

• Minimum, maximum and average time spent on the component