如何通过Vtune Amplifier调用Shell脚本进行应用性能分析？

Hey there! As someone who’s fumbled through messy, mile-long command-line arguments while setting up VTune profiling, I totally get where you’re coming from. Let’s break this down into simple, actionable steps to make your life easier.

Step 1: Create a Shell Script for Your Application #

First, we’ll package all your executable’s parameters into a shell script—this way you won’t have to retype that giant command every time you run VTune.

1. Open a text editor and create a new file (e.g., run_my_app.sh).

2. Add the following content, swapping out the example executable and parameters for your own:

   #!/bin/bash
   
   # Optional: Set any required environment variables here
   # export LD_LIBRARY_PATH="/path/to/your/custom/libs:$LD_LIBRARY_PATH"
   # source /path/to/your/project/env_setup.sh
   
   # Run your application with all its parameters (use backslashes to split long lines)
   /full/absolute/path/to/your/executable \
       --input "/path/to/your/input file with spaces.txt" \
       --num-threads 16 \
       --verbose-log \
       --output-dir "/path/to/save/analysis/results" \
       --complex-flag "special-value-with-hyphens"
   

   Pro tip: Backslashes (\) let you split long commands into readable lines without breaking functionality—super helpful for keeping track of all those parameters.

3. Save the file and make it executable with this command:

   chmod +x run_my_app.sh
   

Step 2: Profile with VTune Using the Script #

Now that your script is ready, using VTune is just as straightforward as profiling a regular executable.

Command-Line Method (amplxe-cl) #

Use VTune’s command-line tool to start your analysis. For example, to run a Hotspots analysis (perfect for finding CPU bottlenecks):

amplxe-cl -collect hotspots -- ./run_my_app.sh

• The -- tells VTune that everything after is the command to run (your script, in this case).
• Swap hotspots with other analysis types like memory-access, threading, or hpc-performance depending on what you’re investigating.

GUI Method #

If you prefer VTune’s graphical interface:

1. Open VTune and create a new project.
2. Under "Launch Application", set:
   • Application path: Select your run_my_app.sh file.
   • Working directory: Choose the directory where your application runs best (usually the same as your executable’s location).
3. Pick your desired analysis type and click "Start"—VTune will handle running the script and collecting data automatically.

Bonus: Make the Script Flexible (Optional) #

If you want to tweak parameters without editing the script every time, add command-line arguments to it. For example:

#!/bin/bash
# Accept input file path and thread count as arguments
INPUT_FILE="$1"
THREAD_COUNT="$2"

/full/absolute/path/to/your/executable \
    --input "$INPUT_FILE" \
    --num-threads "$THREAD_COUNT" \
    --verbose-log \
    --output-dir "/path/to/save/analysis/results"

Then run VTune with your custom parameters like this:

amplxe-cl -collect hotspots -- ./run_my_app.sh "/path/to/new/input.txt" 8

Key Tips to Avoid Headaches #

• Use absolute paths: For your executable, input files, and output directories—this prevents issues if VTune runs from a different working directory than your app.
• Test the script first: Run ./run_my_app.sh on its own before profiling to make sure your application works correctly.
• Include environment setup: If your app relies on specific variables (like library paths), set them directly in the script so VTune inherits them.

内容的提问来源于stack exchange，提问作者prajjwal_jha