VTune Amplifier provides CLI interface.
To get the command line to start analysis that match at GUI please find button "Get Command line" on analysis configuration tab. As for report CLI read this topic.
Could you describe your usage model? For what reasons do you need command line reports? Do you have system limitations which do not allow start GUI on the system?
I have tried this:
you don't need to reload sep. The issue you observe fully relates to an ability to find a proper license file. Could you please check that it is available on the node where you try to generate a report? As I remember it should locate at /opt/intel/licenses if VTune Amplifier was installed from root user.
I don't use license file but a license manager.
I had to reload the sep, because when I run "amplxe-cl collect" on login node, the tool returns:
PMU resources currently being used by another profiling tool or process.
Now, after sep reload, "amplxe-cl collect" hanging with out log
Sorry, I mean "without logs"
Could you try to use a different result directory? If it doesn't help , please set a PERFRUN_DEBUG=1 environment variable, repeat your experiment with a new result directory and upload this result and collected logs? (logs will be located in <result>/log or in working directory).
Great! This means that some garbage left from previous launch (I think it was unsuccessful) in the result directory. Please use an unique result directory to prevent such behavior in future. PERFRUN_DEBUG isn't needed anymore.
About the warnings you see during collection:
These warnings don't mean that sep driver is unloaded it just suggests what you have to do to see kernel related info in your result. Otherwise the time spent in kernel will be attributed in [Outside any known module] So if you don't interested in this info just ignore the warning.
Please check that license file is located in /opt/intel/licenses. If it's set env variable and run report:
but I use Intel license manager:
amplxe: Warning: To profile kernel modules during the session, make sure they are available in the /lib/modules/kernel_version/ location)
We have sep version 4 and 3 in the products. They may be loaded to system at the same time. Every instance of VTune Amplifier will use its version.
Remember! The drivers shall not be in use at the same time. So two collections from different versions of VTune will fail.
answering on your question:
>>Do I have to manually load sep driver on all the nodes?
This depends on your needs. I mean that VTune will try to use driverless Perf based approach if it detects that no driver is loaded. And if it cannot use Perf it will generate an appropriate error message describing what you need to do to get an interested collection result. (SEP driver installation should be an option there).
But if you are interested in SEP driver as a collector by some reason then you will need to load it on all the nodes. Please look at the following article for more details https://software.intel.com/en-us/vtune-amplifier-help-driverless-event-based-sampling-collection
Thanks Vladimir, all clear.
I have tried to load sep4 and sep3 on the same compute nodes, but amplxe-cl don't start:
What user did you launch from? This message seems that VTune failed to disable NMI watchdog. And the only reason I can suppose it happened because of no permissions.
Please try to run a simple no mpi launch. And in case of the same error please try to disable NMI watchdog manually.
Also need to mention that in your second launch with VTune 2015 it will no work so as this version weren't adapted for per node mpi collection, it tried to collect per rank results and corresponding collections conflicted for PMU resources.
Osvaldo, thank you for the report and for your time. This is really confused. I'll try to connect experts in SEP driver to this thread to investigate this issue.
And about suggestions, I suggest to use sep4. And yes, you can use VTune Amplifier 2018 to analyze code compiled with PE-2015, there should not be any problem with that.