A loop summarizes the Total Time for all iterations executed by the loop. Use this pane to explore your source code.
The Call Stack with Loops shows the outer call sites that were executed to reach the current location. The current position in this pane is the top-most entry.
If the Total Time for the source lines is too small a fraction of the total program time to be worth the effort of parallelizing, consider choosing an outer function or loop.
Often a loop is a good place to exploit parallel execution. If the Total Time in this loop is too small, consider choosing a loop further up the call tree with a larger Total Time. If you believe this loop has too many serial dependencies, choose an inner loop in the call tree.
To return to the Survey Report window, click the Survey Report button.
Next Step: Decide Where to Add Annotations
To
propose parallel code regions where you might use parallelism, add annotations
into your sources.
Intel Advisor
Suitability and Dependencies tools use these annotations to predict the likely
parallel characteristics of your program. Each parallel code region (site)
executes one or more tasks, where each task's work can be divided up safely
amongst multiple cores.
If you are not familiar with
Intel Advisor annotations, read the topic
2. Annotate Sources.
You can use the annotation assistant pane to help you add parallel site and task annotations.
The Impact of Parallel Code on Self Time Values
For a parallel code region, the Total Time (and Loop Time) shows the sum of the CPU time for all threads (see the topic Using Partially Parallel Programs with Intel Advisor Tools).