Code Analytics Tab

Tab Purpose and Usage | Tab Location | Tab Regions and Usage

Code Analytics Tab Purpose and Usage

View the most important statistics for a selected loop.

Code Analytics Tab Location

Bottom of the Survey Report and Roofline Analysis window

Code Analytics Tab Regions and Usage

  • Summary: View a quick list of basic information about the loop, such as the code source, whether the loop is scalar or vector, instruction set (and whether extensions, such as VNNI, are used), total time, and the static and dynamic instruction mix.

  • Traits: View additional scalar and vectorization characteristics that may impact performance. For a list of possible traits, see the Data Reference.

  • Trip Counts: View information about the number of times the loop is invoked (trip count), such as the minimum and maximum trip count, the average loop iteration time, etc.

  • Statistics for x: Click the drop-down list at the top of this section to choose to display performance statistics for a specific operation type: FLOP, INTOP, INT + FLOAT, or All Operations.

    Click the toggle control to switch between displaying performance statistics using self or total loop metrics.

  • Code Optimizations: View a list of code optimizations applied to the loop by the compiler, as well as information on which compiler was used and what version. This information is only available for binaries compiled by the Intel® C, C++, or Fortran Compilers.

  • Roofline: View a more detailed roofline chart that summarizes recommendations and information from the Roofline Conclusions section, such as whether the loop is compute bound, memory bound, or both.

    This chart features the labeled distance between the loop and the performance roof limiting it. The metrics used to plot the loop on the chart, Giga OPS (operations per second) and AI (arithmetic intensity), are also displayed.

    Note

    This control requires that you set the environment variable ADVIXE_EXPERIMENTAL to roofline_guidance.

For more complete information about compiler optimizations, see our Optimization Notice.