analytics
proiv dashboard
|
analytics |
proiv dashboard |
|
Configuring ProfilerProfiler
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
Profiler Configuration
To view the PROIV Profiler configuration, do the following:
On the Analytics Settings tab, view PROIV Profiler.
The configuration page displays the settings.
Currently this only shows details of the trace file path. This is readonly.
|
Field Name |
Description |
|
Trace File Path |
The folder path that generated profiler trace files will be stored in. This path property is used by both the Virtual Machine and Analytics deployments, it can only be configured via the Virtual Machine - Settings - Profiler settings and is shown display only here for reference. The default path on a Windows machine is "&$@~PROPATH/../profiler_traces" |
Note: By default, .P4P is the extension of the trace file. The .P4P file extension is changed to .p4a representing the file is analyzed. A zip folder is created with P4P File, GRIDSON File (stores data to represent in the form of Grid in the Profiler screen) and TREESON File (stores data to represent in the form of Tree in the Profiler screen) in the place of P4P file. In case of any processing errors, an alert appears with Data Load error. Refer to Analyzing Profiler Results for more information.
Configuring Code Coverage
Code Coverage Configuration
To view the PROIV Code Coverage configuration, do the following:
On the Analytics Settings tab, view PROIV Code Coverage.
The configuration page displays the settings.
Currently this only shows details of the code coverage file path. This is readonly.
|
Field Name |
Description |
|
Code Coverage File Path |
The folder path that generated code coverage files will be stored in. This path property is used by both the Virtual Machine and Analytics deployments, it can only be configured via the Virtual Machine - Settings - Code Coverage settings and is shown display only here for reference. The default path on a Windows machine is "&$@~PROPATH/../codecoverage" |
Note: By default, .p4cc is the extension of the coverage file.
Topic ID: 820003