Visible to Intel only — GUID: GUID-4C9EBFD6-9D84-44EA-ADAC-EB734CEF2C97
Visible to Intel only — GUID: GUID-4C9EBFD6-9D84-44EA-ADAC-EB734CEF2C97
custom-collector
Launch an external collector to gather custom interval and counter statistics for your target in parallel with the VTune Profiler.
GUI Equivalent
Configure Analysis window > WHAT pane
Syntax
-custom-collector=<string> |
Arguments
<string> |
Command line launching an external collection tool. |
Actions Modified
Description
Your custom collector can be an application you analyze with the VTune Profiler or a collector that can be launched with the VTune Profiler.
Use the -custom-collector option to specify an external collector other than a target analysis application.
When you start a collection, the VTune Profiler does the following:
Launches the target application in the suspended mode.
Launches the custom collector in the attach (or system-wide) mode.
Switches the application to the active mode and starts profiling.
If your custom collector cannot be launched in the attach mode, the collection may produce incomplete data.
You can later import custom collection data (time intervals and counters) in a CSV format to the VTune Profiler result.
Example
This example runs Hotspots analysis in the default user-mode sampling mode and also launches an external script collecting custom statistics for the specified application:
Windows:
vtune -collect hotspots -custom-collector="python.exe C:\work\custom_collector.py" -- notepad.exe
Linux:
vtune -collect hotspots -custom-collector="python /home/my_collectors/custom_collector.py" -- my_app
This example runs VTune Profiler event-based sampling collector and also uses an external system collector to identify product environment variables:
Windows:
vtune -collect-with runsa -custom-collector="set | find \"AMPLXE\"" -- notepad.exe
Linux:
vtune -collect-with runsa -custom-collector="set | find \"AMPLXE\"" -- my_app