Why Not Offloaded: Cannot Be Modeled
Cause and Solution
Cause and Details
Cannot be modeled: Outside of Marked Region
Offload Advisor cannot model performance for a code region because it is not marked up for analysis.
Cannot be modeled: Not Executed
A code region is in the call tree, but the Offload Advisor detected no calls to it for a dataset used during Survey.
This can happen if execution time of the loop is very small and close to the sampling interval of the Intel® Advisor. Such loops can have significant inaccuracies in time measurement. By default, the sampling interval for Survey is 0.01 seconds.
You can try to decrease the sampling interval of the Intel Advisor:
Cannot be modeled: Internal Error
Internal Errormeans incorrect data or lack of data because the Offload Advisor encountered issues when collecting or processing data.
For example, the internal error can happen if:
Cannot be modeled: System Module
This code region is a system function/loop.
This is not an issue. If this code region is inside an offload region, or a runtime call, its execution time is added to execution time of offloaded regions.
Cannot be modeled: No Execution Count
The Offload Advisor detected no calls to a loop during Trip Count analysis and no information about the Execution Counts is available for this loop.
This can happen if the Offload Advisor incorrectly attributed metrics collected to the application call tree.
Verify the issue:
If the call tree is not broken and the
Average Trip Countsreport zero or no value, there is a problem with metrics attribution.
Try to rerun the collection and performance projection to fix the metrics attribution problem.