how to get the wall time of special code line?

I found from https://software.intel.com/en-us/vtune-amplifier-help-openmp-analysis-fr... that we can use "amplxe-cl <action> <analysis_type> -knob analyze-openmp=true" to do openmp profiling. 

However when I execute the command on our linux server installed with vtune2019, it cannot recognize -knob analyze-openmp. 

See below:

amplxe-cl -quiet -collect="hotspots" -knob analyze-openmp=true  -data-limit=0 -finalization-mode=none -- myapp.exe         

amplxe: Error: Cannot find knob analyze-openmp. For a list of available knobs, use –help collect hotspots

Could someone help me with this?

Hey guys,

I'm profiling my SPDK app which obviously keeps all "reactor" CPUs busy even if there's no useful activity (SPDK's polling model). I'd like to permanently filter out those "idle time" functions from my Amplifier views, according to the function list I can provide.

Right now, in order to see effective CPU utilization (without SPDK's "idle" activity) on the time line I have to manually filter out dozens of spdk_*, rte_* and nvme_* functions, which is quite inconvenient.

Thanks!
Maxim

Whenever I try to use Hardware Event-Based Sampling in VTune, I get the following two error messages:
This analysis type is not applicable to the system because VTune Amplifier cannot recognize the processor. If this is a new Intel processor, please check for an updated version of VTune Amplifier. If this is an unreleased Intel processor, please contact Online Service Center for an NDA product package.
This analysis type is not applicable to the current machine microarchitecture.

I'm using a laptop with an Intel Core i7-4710HQ @ 2.50GHz [Intel64 Family 6 Model 60 Stepping 3, GenuineIntel].

Whenever I try to use Hardware Event-Based Sampling in VTune, I get the following two error messages:
This analysis type is not applicable to the system because VTune Amplifier cannot recognize the processor. If this is a new Intel processor, please check for an updated version of VTune Amplifier. If this is an unreleased Intel processor, please contact Online Service Center for an NDA product package.
This analysis type is not applicable to the current machine microarchitecture.

I'm using a laptop with an Intel Core i7-4710HQ @ 2.50GHz [Intel64 Family 6 Model 60 Stepping 3, GenuineIntel].

I'm using Intel Parallel Studio XE, and I see every now and then there are updates. I was wondering what's the proper way on Linux to check and auto update, instead of manually downloading from the website the new version of Parallel Studio XE and installing it.

I used type <uarch-exploration> to collect performance data of my openmp offload benchmarks.

In the bottom-up tab, I found the most hottest function is a kernel function with unknown name(from vmlinux). And when I expand it to see the caller, vtune shows no call stack information. See attached image.

I wonder how this happened and what does this mean. Could anyone give me some help?

Hello,

I'm seeking information on a way to profile multiple Xen guest domains (domUs) on a symmetric multiprocessor server using SSH. The server is running Ubuntu Server. I need to collect hardware event information from Xeon (Skylake) processors, while utilizing Cache Monitoring Technology (CAT) and Cache Monitoring Technology to calculate the throughput of each domU while they are executing applications.

Originally, I tried using OProfile version 0.9.5 patched with Xenoprof version 0.9.5. In doing this, I encountered errors indicating this version of OProfile is not supported by the kernel, architecture, or processors. To this end, I've tried installing VTune Amplifier on the host operating system (dom0), running on real hardware, as well as a domU, running on the Xen hypervisor, to collect the necessary data to calculate the throughput of each domU. However, the VTune Amplifier installer recognizes dom0 and a domU as virtual machines leading to the sampling drivers for hardware event-based sampling not being installed.

Is it possible to use VTune Amplifier to profile multiple domUs instead of just one domU? Can VTune Amplifier be used to calculate the throughput of each domU? Why is the VTune Amplifier installer indicating dom0 as a virtualized system when dom0 runs on real hardware?

Would it be more beneficial to build a new machine with Xeon processors and use a desktop version of Ubuntu to use VTune Amplifier? If so, which Xeon processor is recommended?

Your advice is very much appreciated.

Thank you.

Hey,

I am using ue analysis to profile a set of applications with different hardware. So far, I've used Ubuntu 18.04 with
a) Intel(R) Xeon(R) CPU E5-2640 v3 @ 2.60GHz
b) Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz
c) Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz

When I run my applications with the less powerful CPU on my desktop, the results are showing what I expect and everything works fine.

However, when I run them to the servers (each has two sockets of either CPU a) or b)), the results become weird. I've run more than 100 different workloads (applications and configurations) that return a Core Bound metric equal to 0. But that's not the only problem. While, Memory Bound is a sub-category of BE-bound, it shows that its pipeline percentage is higher than BE-Bound, which results in a graph with components that add up to more than 100% of pipeline slots! E.g., I end up having Bad-Spec=3.6%, FE-Bound=7%, Retiring=27.4% and Memory-Bound=75%, which gives me 113%!

Has anyone seen anything similar? Do you have any suggestions on how I could resolve this? I've already tried upgrading the kernel...

Cheers,
George

I want to question about the meaning of -data-limit options.

I'm using the command line interface to profile the application with --data-limit=0 option.

The problem is that, the total size of result directory is too big. I have to measure metrics with different environment many times, but I cannot do it because of the limited storage. In documentation, default data-limit is enough in normal case. But I'm not sure about this because the application I'm profiling is the PyTorch python script training complex CNN models.

In has the data preprocessing, data loading, training(forward & backward), validating(only forward) code. And with default data-limit, the measurement ends too early and I don't think this result represents the overall characteristic of my Python script. Could you provide me any tip about this situation?

+) I have one more question about hardware event-based sampling in the collection mode threading. The elapsed time in this mode is about 20% longer than other mode (hotspots, memory access) Why it happened? And when I writes a report about this analysis, which elapsed time will be meaningful to readers do you think?

I've profiled a PyTorch code, that is executed on the 16-core Xeon CPU. And now, I'm profiling the same code on the environment consisting of 4-core CPU and NVIDIA Titan XP. I'm using some NVIDIA GPU profiling tools.

In this point, I'm curious about the results when I use VTune amplifier to profile in the second environment I've mentioned. Do you think this will cause error? Or just generate report that is different from CPU-only environment?

I'm using amplxe-cl to collect locksandwaits on a running process.

/opt/intel/vtune_amplifier/bin64/amplxe-cl -collect locksandwaits -target-pid=9929

I got the error:

amplxe: Warning: The analysis type 'locksandwaits' is deprecated. Use 'threading' analysis type instead. See more details with 'amplxe-cl -help collect threading'.
amplxe: Collection started. To stop the collection, either press CTRL-C or enter from another console window: amplxe-cl -r /data1/sunkaicheng/indigo/brec_indigo_recall/build/r002lw -command stop.
amplxe: Warning: Cannot stop posix timer: __NR_timer_settime() system call returned -1.
amplxe: Collection detached.
amplxe: Collection stopped.
amplxe: Using result path `/data1/sunkaicheng/indigo/brec_indigo_recall/build/r002lw'
amplxe: Executing actions 50 % done
amplxe: Error: 0x40000003 (Unexpected internal error / invalid state) -- locale::facet::_S_create_c_locale name not valid

system: ubuntu 16.04

kernal: 4.9.70-040970-generic

CPU: Intel(R) Xeon(R) Silver 4110 CPU @ 2.10GHz

Windows 10

Intel(R) VTune(TM) Amplifier 2019 Update 6

MS Visual Studio 2019

intel i5 750, 8gb ddr3

Hello! 

Even after reinstalling ms visual studio and parallel studio xe vtune doesnt run in visual studio ide. when execute vtune in his own gui by user mode sampling i get this error when is collecting results. i cant also run in hardware event mode sampling because vtune doesnt recognize my processor.

log of installation is attached.

thank you for your help

""""""""""""""""""

Exception]
Address: 0x00007ff9fed4fadd
Code: 0x00000000c0000094
CrashedPID: 7768
CrashedTID: 7772
Description: EXCEPTION_INT_DIVIDE_BY_ZERO
Module: 
Product: Intel(R) VTune(TM) Amplifier 2019 Update 6; 602217
ReportPath: C:\Users\HENRIQ~1\AppData\Local\Temp\amplxe-log-Henrique Gropelli\2019-11-21-14-28-46-683.amplxe-backend.exe\

[Process]
Process Name: amplxe-backend.exe
Virtual Memory Size: 4742360K
Working Set Size: 221460K

[Dump]
Path: C:\Users\HENRIQ~1\AppData\Local\Temp\amplxe-log-Henrique Gropelli\2019-11-21-14-28-46-683.amplxe-backend.exe\crash.dmp

[PremortalLog]
6709 [8000] ERROR apiservice <> - getStatus() == ServiceStatus::Running
C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp(199): apisvc1::Service::getHttpPort
, at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp:199
6772 [8000] ERROR apiservice <> - getStatus() == ServiceStatus::Running
C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp(199): apisvc1::Service::getHttpPort
, at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp:199
6834 [8000] ERROR apiservice <> - getStatus() == ServiceStatus::Running
C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp(199): apisvc1::Service::getHttpPort
, at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp:199
6897 [8000] ERROR apiservice <> - getStatus() == ServiceStatus::Running
C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp(199): apisvc1::Service::getHttpPort
, at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp:199
6959 [8000] ERROR apiservice <> - getStatus() == ServiceStatus::Running
C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp(199): apisvc1::Service::getHttpPort
, at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp:199
7022 [8000] ERROR apiservice <> - getStatus() == ServiceStatus::Running
C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp(199): apisvc1::Service::getHttpPort
, at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp:199
7084 [8000] ERROR apiservice <> - getStatus() == ServiceStatus::Running
C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp(199): apisvc1::Service::getHttpPort
, at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp:199
7134 [8000] ERROR apiservice <> - getStatus() == ServiceStatus::Running
C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp(199): apisvc1::Service::getHttpPort
, at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\apiservice1\src\service.cpp:199
7212 [7544] ERROR cfgmgr <> - Cannot find context value: targetOS., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
7227 [7544] ERROR cfgmgr <> - Cannot find context value: targetOS., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
28099 [3556] ERROR cfgmgr <> - Cannot find context value: targetOS., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
28109 [3556] ERROR cfgmgr <> - Cannot find context value: targetOS., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
28340 [7368] ERROR cfgmgr <> - Errors happened during transformation
28340 [7368] ERROR cfgmgr <> - %ThisTargetTypeOnlyForADB
28341 [7368] ERROR cfgmgr <> - Errors happened during transformation
28341 [7368] ERROR cfgmgr <> - %ThisTargetTypeNotWorking
28378 [5280] ERROR cfgmgr <> - Errors happened during transformation
28378 [5280] ERROR cfgmgr <> - %ThisTargetTypeOnlyForADB
28379 [5280] ERROR cfgmgr <> - Errors happened during transformation
28379 [5280] ERROR cfgmgr <> - %ThisTargetTypeNotWorking
29535 [7368] ERROR cfgmgr <> - Errors happened during transformation
29535 [7368] ERROR cfgmgr <> - %ThisAnalysisTypeIsNotApplicable
29552 [7368] ERROR cfgmgr <> - Errors happened during transformation
29552 [7368] ERROR cfgmgr <> - %ThisAnalysisTypeIsOnlyForAndroidAndLinux
29559 [7368] ERROR cfgmgr <> - Errors happened during transformation
29559 [7368] ERROR cfgmgr <> - %ThisAnalysisTypeIsNotApplicable
29568 [7368] ERROR collectionapi <> - pSetting
C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\collectionapi1\src\collection_configuration_context.cpp(953): collectionapi_1::CollectionConfigurationContext::getCurrentCollectorId
, at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\collectionapi1\src\collection_configuration_context.cpp:953
29568 [7368] ERROR cctrl.exchange <> - (!collector.is_null()) && (!to.is_null()) 'gh2::error::IsNot.Valid.Argument:'
C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cctrl2\core\target_session.cpp(82): cctrl2::BaseTargetSession::putCollectorContext
, at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cctrl2\core\target_session.cpp:82
29624 [3556] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
29624 [3556] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
29626 [3556] ERROR cfgmgr <> - Cannot find context value: showInlinesByDefault., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
29662 [3556] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
29663 [3556] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
29666 [3556] ERROR cfgmgr <> - Cannot find context value: showInlinesByDefault., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
29714 [5280] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
29714 [5280] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
29716 [5280] ERROR cfgmgr <> - Cannot find context value: showInlinesByDefault., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
29742 [5280] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
29742 [5280] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
36626 [3556] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
36626 [3556] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
36628 [3556] ERROR cfgmgr <> - Cannot find context value: showInlinesByDefault., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
36654 [3556] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
36654 [3556] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
37867 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
37867 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
37868 [7772] ERROR cfgmgr <> - Cannot find context value: showInlinesByDefault., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
37920 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
37920 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
37938 [7772] ERROR cfgmgr <> - Cannot find context value: targetOS., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
37947 [7772] ERROR cfgmgr <> - Cannot find context value: targetOS., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
51850 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
51850 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
51900 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
51901 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
51961 [7772] ERROR cfgmgr <> - (outputBag != 0) && (inputBag != 0) && !m_ctx.is_null() 'gh2::error::FailedTo.Process.The.Parameter:'
C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp(1769): cfgmgr2::RuleProcessor::process
, at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:1769
51992 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
51992 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52007 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52007 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52054 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52054 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52159 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52159 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52179 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52179 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52636 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52636 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52670 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384
52671 [7772] ERROR cfgmgr <> - Cannot find context value: clockticksEventName., at file: C:\BB\INNLphep2w6r\b\b\tmpc4wosy\vcs\cfgmgr2\src\rules.cpp:384

[Context.0x00001e5c]
EAX: 0x0000000000000000
EBP: 0x000000b5482f7ed0
EBX: 0x000000b5482f8490
ECX: 0x000002a1c39e0c48
EDI: 0x000000b5482f8768
EDX: 0x0000000000000000
EIP: 0x00007ff9fed4fadd
ESI: 0x0000000000000000
ESP: 0x000000b5482f7e90
R10: 0x0000000000008000
R11: 0x000000b5482f7d00
R12: 0x0000000000000001
R13: 0x0000000000000000
R14: 0x000000b5482f86c8
R15: 0x000000b5482f8f50
R8: 0x000002a1c39e0be8
R9: 0x000002a1c39e0be0

""""""""""""""

When using 2019 vtune to profile memory consumption. after attaching PID, it immediately errors out and crashes the process I try to profile. I'm using it in debian 9. wondering if anyboyd experienced such issue.

Hi, we're potentially looking to try VTune profiler (and Intel Advisor). Looking at the FAQ there is a free community support license which is fine for us, but what's not clear is if it's still free for commercial use under the community license - could you confirm if that's the case, or if there are any better links that explain this please.

Do Vtune and Advisor both come under the same free community license?

Hi,

I am working with Intel’s vtune performance analyser for various workloads in HPC.

Is there a way I can summarize my runtime analysis as a csv file for each thread ?

Currently I am summarizing vtune analysis to csv using

$ amplxe-cl -report hotspots -result-dir PATH/TO/DIR/ -format=csv -report-output /PATH/TO/SOMETHING.csv

But this command removes per-thread information and only gives me an overall view of the complete application. I want a per thread summary in csv format. I know this can be done on the gui but that’s a lot of manual work and a command line version could be very useful for automation.

Hello Intel Team,

I'm trying to run an academic license of VTune 2019 on a linux server with a simple Python file, test.py. I used the command line interface to collect data using: amplxe-cl -collect hotspots -r vtune_test_hotspots_results -run-pass-thru=--no-altstack python test.py I used the argument -run-pass-thru=--no-altstack based on multiple sources to remove an initial error about the stack size being too small

Source 1: http://hpc.ipp.ac.cn/wp-content/uploads/2015/12/documentation_2016/en/vt...

Source 2: https://scc.ustc.edu.cn/zlsc/tc4600/intel/2017.0.098/vtune_amplifier_xe/...

I used amplxe-gui with X11 forwarding to view the results on my local machine (MacOS). However, I can only view the assembly code, as shown in the screenshot below. Can you please help me understand what I must do to view the source code? For some reason, I was not allowed to upload a .py file so simply change the extension to test.py and run with Python 3.7 to reproduce my issue. The file takes ~10 seconds to run. The output displayed at the command line has also been included below. I'm wondering if the warning "amplxe: Warning: Cannot locate debugging information for file ..." is part of the issue. Please let me know how to resolve that.

From reading other forum posts, I found some potential options such as specifying a search path and using Intel’s JIT Profling API, but I am unsure how to implement these or if there is a better/easier way to approach this problem. Thank you for your help.

Hi,

I've tried several times in multiple browsers, but VTune Profiler is not downloading for me.

Best regards,

Stewart

Good day.

I'am new user of Vtunes. My main question is Why Vtunes hasn't it's own ssh client? Do I write understand that I should use Putty as ssh-client, not other application? What should I do if my ssh client is SecureCRT? Where could I read about mechanism of coworking with Vtunes and Putty? Now I has such problem: I have ssh connection with Putty with ssh-key with passphrase. When I type username@host_name, Vtunes answer: "Cannot communicate with target, Please check password-less authentication request". But when I type wrong_username@host_name, Vtunes answer "Server refused our key". Does problem in ssh-key passphrase?

Dear All,

I'm not able to get source code view for NetCore 3.1.100 application. Proof of concept app is compiled with full debug info. PDB and source file location is provided. VTune is launched with admin permissions. I'm trying to follow guidelines from https://devblogs.microsoft.com/dotnet/net-core-source-code-analysis-with... but no matter what options are selected I have no luck getting source code view.

Product versions:

• Inter VTune Amplifier 2019 Update 8
• Visual Studio 2019 16.4.1
• NetCore 3.1.100

VTune is not complaining about missing sources or PDBs (see screen). Can anyone point me in the right direction?

Best Regards & thanks in advance,

Marcin Ostrowski