Result Interpretation
After running the
Offload Modeling perspective with
Low accuracy, you get a basic
Offload Modeling report, which shows you estimated performance of your application after offloading to a target platform assuming it is mostly bounded by compute limitations.
Offload Modeling with
Low accuracy assumes that:
- There is no tax for transferring data between baseline and target platforms.
- All data goes to L1/L3 cache level only. L1/L3 cache traffic estimation might be inaccurate.
- A loop is parallel if the loop dependency type in unknown (Assume Dependencies checkbox is disabled). This happens when there is no information about a loop dependency type from a compiler or the loop is not explicitly marked as parallel, for example, with a programming model (OpenMP*, Data Parallel C++,
Intel® oneAPI Threading Building Blocks (oneTBB))
Note
This topic describes data as it is shown in the
Offload Modeling report in the Intel Advisor GUI. You can also view the results using an HTML report, but data arrangement and some metric names may vary.
In the Offload Modeling report:
Review the metrics for the whole application in the
Summary tab.
- Check if your application is profitable to offload to a target device or if it has a better performance on a baseline platform in the
Program Metrics panes.
- See what prevents your code from achieving a better performance if executed on a target device in the
Offload Bounded by pane.
Note
If you enable
Assume Dependencies option for the
Performance Modeling analysis, you might see high percentage of dependency-bound code regions. You are recommended run the
Dependencies analysis and rerun Performance Modeling to get more accurate results.
- If the estimated speed-up is high enough and other metrics in the
Summary pane suggest that your application can benefit from offloading to a selected target platform, you can start offloading your code.
If you want to investigate the results reported for each region in more detail, go to the
Accelerated Regions tab and select a code region:

For details about metrics reported, see
Accelerator Metrics.