Known issue collecting FLOPS data with Intel® Advisor 2017 Update 3

Problem:

FLOPS and all related data, including Roofline data are completely missed if a survey is collected with the –no-auto-finalize option.

Affected customers:

It should mostly affect our Intel® Xeon Phi™ processor (codename: Knights Landing) customers, because we recommend they perform remote finalization to avoid significant overheads.

Steps to reproduce:

1. Collect survey with –no-auto-finalize option

2. Collect FLOPS data

3. Finalize/open results and discover that FLOPS and all related data are missing (including Roofline)

Root cause:

There is an issue with filtering of FLOPS data. The collector always looking for callstack information, even if this mode is disabled. However, this information is only available after survey finalization. Therefore, no data is collected if survey finalization was skipped.

Workarounds:

1. Perform survey finalization before collecting FLOPS data. It may be done both on remotely or locally on the  Intel® Xeon Phi™ (not recommended because of the overhead)

2. Same as above, but you can reuse the callstacks.def from <advisor_project_dir>\e000\callstacks.def for further collections of the same application (if there are no changes in the application modules/callstack, in other case some data may be missed)