When the Modules category is selected in the Explorer panel, the Report panel displays profiling results for each module of your application. The panel contains several columns that do not depend on the active counter and there is also a set of columns that depend on the counter that was used during profiling.
Columns That Do Not Depend on The Active CounterColumns That Do Not Depend on The Active Counter
| Columns (in alphabetical order) | Description |
|---|---|
| Module Name | Name of the module. |
| Exceptions (#) | This value is a sum of all Exception values of routines that belong to the module. It indicates the total number of times the methods belonging to the module were entered but not successfully exited. This is usually the number of exception exits in the module’s routines. |
| Hit Count | The number of routine calls that were profiled. See also Skip Count. This value is a sum of the Hit Count result of all profiled routines that belong to the given module. |
| Skip Count | Number of times the routines were excluded from profiling, because the profiling status was off (This can be, for example, the number of times the routines were affected by off-triggers). This value is a sum of the Skip Count result of all profiled routines that belong to the given module. |
Columns That Depend on The Active Counter
| Counters | Columns | Description |
|---|---|---|
| Elapsed Time, User Time, User+Kernel Time |
Time | The total execution time (excluding child calls) of routines that are defined in the module. This is a sum of the Time results of all profiled routines that the given module contains. |
| % Time | Total time spent for execution of profiled routines that belong to the given module as a percentage of the sum of the Time column values for all modules that are displayed in the Report panel. | |
| CPU Cache Misses | Misses | The total number of CPU cache misses that occurred during profiling of routines that the given module contains. This is a sum of the Misses result value of all routines that the given module contains. |
| % Misses | Total number of cache misses as a percentage of the sum of the Misses column values for all modules that are displayed in the Report panel. | |
| CPU Mispredicted Branches | Branches | The total number of code branches that were mispredicted during profiling of routines that the given module contains. This is a sum of the Branches result of all profiled routines that the given module contains. |
| % Branches | Total number of mispredicted branches as a percentage of the sum of the Branches column values for all modules that are displayed in the Report panel. | |
| Hard Memory Page Faults, Soft Memory Page Faults, All Memory Page Faults |
Faults | The total number of memory page faults that occurred during profiling of routines that the given module contains. This is a sum of the Faults result value of all profiled routines that the given module contains. |
| % Faults | Total number of memory page faults as a percentage of the sum of the Faults column values for all modules that are displayed in the Report panel. | |
| Split Load Replays, Split Store Replays, Blocked Store Forwards Replays |
Replays | The total number of replays that occurred during profiling of routines that the given module contains. This is a sum of the Replays result value of all profiled routines that the given module contains. |
| % Replays | Total number of replays as a percentage of the sum of the Replays column values for all modules that are displayed in the Report panel. | |
| 64K Aliasing Conflicts | Conflicts | The total number of aliasing conflicts that occurred during profiling of routines that the given module contains. This is a sum of the Conflicts result value of all profiled routines that the given module contains. |
| % Conflicts | Total number of aliasing conflicts as a percentage of the sum of the Conflicts column values for all modules that are displayed in the Report panel. | |
| Context Switches | Switches | The total number of context switches that occurred during profiling of routines that the given module contains. This is a sum of the Switches result value of all profiled routines that the given module contains. |
| % Switches | Total number of context switches as a percentage of the sum of the Switches column values for all modules that are displayed in the Report panel. |
A replay is an attempt of executing a micro-operation
when conditions for the correct execution of this operation are not satisfied.
Replays may be caused by cache misses, store forwarding issues, etc.
Normally, certain number of replays always occur during the application
execution. However, a superfluous number of replays designates a
performance problem.
when conditions for the correct execution of this operation are not satisfied.
Replays may be caused by cache misses, store forwarding issues, etc.
Normally, certain number of replays always occur during the application
execution. However, a superfluous number of replays designates a
performance problem.
See Also
Performance Profiler - Report Panel
About the Report Panel
Results of the Modules Category