Intel Advisor runs very slowly

[Stephen_V_]

I am running Intel Advisor 2017 in Visual Studio 2012. I've been able to work through the tutorial using the vec_samples example code.

However, in the code that I am actually working on, the Advisor takes a really long time to process the results of a run of a simple test harness.

This is the output from the Intel Advisor 2017 messages window:

Collection has been started.
Peak bandwidth measurement started.
Peak bandwidth measurement finished.
Collection has stopped. Application exit code:  0
Raw data has been loaded to the database, elapsed time is 0.003 seconds.
Finalizing the result took 18.101 seconds.
Collection time: 26s
Finalizing results
Finalizing the result
Clearing the database
The database has been cleared, elapsed time is 0.198 seconds.
Loading raw data to the database
Loading 'systemcollector-3664-steve-PC.sc' file
Loading '8532-1668.0.trace' file
Loading 'tripcounts_6176_0.tcs' file
Updating precomputed scalar metrics
Raw data has been loaded to the database, elapsed time is 2.395 seconds.
Processing profile metrics and debug information
Data transformations have been finished, elapsed time is 0.000 seconds.
Setting data model parameters
Resolving module symbols
Resolving information for `WS2_32.dll'
Resolving information for `MSVCR110.dll'
Resolving information for `ntmarta.dll'
Warning: Cannot locate debugging symbols for file `C:\Windows\system32\WS2_32.dll'.
Resolving information for `ntdll.dll'
Resolving information for `GDI32.dll'
Resolving information for `MSVCR80.dll'
Resolving information for `IP2Lib64.dll'
Resolving information for `svml_dispmd.dll'
Warning: Cannot locate debugging symbols for file `C:\Windows\SYSTEM32\ntmarta.dll'.
Warning: Cannot locate debugging symbols for file `C:\Windows\SYSTEM32\ntdll.dll'.
Warning: Cannot locate debugging symbols for file `C:\Windows\system32\GDI32.dll'.
Warning: Cannot locate debugging symbols for file `C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_88dcdb0b2fb19957\MSVCR80.dll'.
Resolving information for `clr.dll'
Resolving information for `combase.dll'
Resolving information for `System.ni.dll'
Warning: Cannot locate debugging symbols for file `C:\Windows\SYSTEM32\combase.dll'.
Resolving information for `wminet_utils.dll'
Warning: Cannot locate debugging symbols for file `C:\Windows\assembly\NativeImages_v4.0.30319_64\System\9e5716401a8897f73f47ad27f58b8518\System.ni.dll'.
Resolving information for `mscorlib.ni.dll'
Warning: Cannot locate debugging symbols for file `C:\Windows\Microsoft.NET\Framework64\v4.0.30319\wminet_utils.dll'.
Resolving information for `mswsock.dll'
Warning: Cannot locate debugging symbols for file `C:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\35a36d5faf5966eed2243f3d43f9f490\mscorlib.ni.dll'.
Warning: Cannot locate debugging symbols for file `C:\Windows\system32\mswsock.dll'.
Resolving information for `tpsstool.dll'
Warning: Cannot locate debugging symbols for file `C:\Program Files (x86)\IntelSWTools\Advisor 2017\bin64\tpsstool.dll'.
Resolving information for `KERNELBASE.dll'
Warning: Cannot locate debugging symbols for file `C:\Windows\system32\KERNELBASE.dll'.
Resolving information for `AI2Interface.dll'
Resolving information for `clrjit.dll'
Resolving information for `mscoreei.dll'
Warning: Cannot locate debugging symbols for file `C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll'.
Warning: Cannot locate debugging symbols for file `C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll'.
Resolving information for `System.Management.ni.dll'
Resolving information for `RPCRT4.dll'
Warning: Cannot locate debugging symbols for file `C:\Windows\system32\RPCRT4.dll'.
Warning: Cannot locate debugging symbols for file `C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Management\9f633e32d6de1c9d04fb2008f1e001bb\System.Management.ni.dll'.
Resolving information for dangling locations
Resolving information for `MSVCR120_CLR0400.dll'
Resolving information for `fastprox.dll'
Warning: Cannot locate debugging symbols for file `C:\Windows\SYSTEM32\MSVCR120_CLR0400.dll'.
Warning: Cannot locate debugging symbols for file `C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll'.
Warning: Cannot locate debugging symbols for file `C:\Windows\system32\wbem\fastprox.dll'.
Resolving information for `RunUnitTestsAI2Interface.exe'
Resolving information for `KERNEL32.DLL'
Warning: Cannot locate debugging symbols for file `C:\Windows\system32\KERNEL32.DLL'.
Resolving bottom user stack information
Resolving thread name information
Resolving call target names for dynamic code
Symbol resolution has been finished, elapsed time is 51.205 seconds.
Processing profile metrics and debug information
Deferred data transformations have been finished, elapsed time is 5184.648 seconds.
Setting data model parameters
Data model parameters have been set, elapsed time is 0.345 seconds.
Precomputing frequently used data
Precomputing frequently used data
Updating precomputed scalar metrics
Precomputing frequently used data has been finished, elapsed time is 0.066 seconds.
Discarding redundant overtime data
Saving the result
Redundant overtime data has been discarded, elapsed time is 0.003 seconds.
Raw collector data has been discarded, elapsed time is 0.000 seconds.
Finalizing the result took 5376.563 seconds.
Preparing data for display of survey call tree
Resolving module symbols
Resolving bottom user stack information
Resolving thread name information
Resolving call target names for dynamic code
Precomputing frequently used data
Finalization time: 01:29:41s
Data collection processing end

There are a couple of steps that take 5000+ seconds.

Does anyone have any suggestions as to what is happening? Running the test again seems just as slow. Task manager shows VS running at 20% CPU.

Regards,

Steve

[TimP]

I've found it important to avoid excessive number of threads (1t/core, OMP_PLACES=cores).  I suppose that default sampling interval ought to be suitable for a 26 second collection, but I've found it difficult to set a sampling interval which gives good resolution without excessive analysis time.  Still, analysis does tend to take around 40 times as long as collection, even without bandwidth measurements, which haven't worked for me.