Intel® Advisor Help
Run the specified type of analysis and collect data.
Workflow
Toolbar
File > New > Start [Name] Analysis
-c=<string> [--action-options] [--global-options] [[--] <target> [<target options>]] --collect=<string> [--action-options] [--global-options] [[--] <target> [<target options>]] |
<string> is the type of analysis:
Argument |
Description |
---|---|
dependencies |
Collect dependencies data to predict and eliminate data sharing problems. |
map |
Collect memory access patterns data. |
roofline |
Special batch mode of data collection that runs the Survey analysis immediately followed by the Trip Counts & FLOP analysis. |
suitability |
Collect suitability data by executing annotated code to analyze the proposed threading parallelism opportunities and estimate where performance gains are most likely. |
survey |
Survey the target (your executable application) and collect data about code that may benefit from (more) parallelism. |
tripcounts |
Collect the following data and add it to the Survey report: loop iteration, floating-point and integer operation, and memory traffic statistics, and more. |
No default argument
app-working-dir, auto-finalize, benchmarks-sync, cache-config, cachesim-associativity, cachesim-cacheline-size, cachesim-mode, cachesim-sets, data-limit, delete-tripcounts, duration, enable-cache-simulation, exclude-files, executable-of-interest, filter-by-scope, filter-reductions, flop, ignore-app-mismatch, ignore-checksums, instance-of-interest, integrated, interval, loop-call-count-limit, loops, mark-up, mark-up-list, mkl-user-mode, module-filter, module-filter-mode, mrte-mode, option-file, profile-python, project-dir, quiet, record-mem-allocations, record-stack-frame, refinalize-survey, resume-after, return-app-exitcode, search-dir, spill-analysis, stack-stitching, stacks, stack-walk-mode, start-paused, static-instruction-mix, stop-after, strategy, support-multi-isa-binaries, target-pid, target-process, trace-mode, trace-mpi, track-stack-variables, trip-counts, verbose
Survey the application to find candidates for code that may benefit from (more) parallelism.
$ advixe-cl --collect=survey --project-dir=./advi --search-dir src:r=./src -- ./bin/myApplication
Collect memory access patterns data on the specified loops.
$ advixe-cl --collect=map --mark-up-list=5,10,12 --project-dir=./advi --search-dir src:r=./src -- ./bin/myApplication
Collect survey data on four nodes of an MPI cluster into the shared ./advi project directory.
$ mpirun -n 4 advixe-cl --project-dir=./advi --collect=survey -- <PATH>/mpi-sample/1_mpi_sample_serial
Collect dependencies data for all innermost loops that account for over 2% of the total CPU time.
$ advixe-cl --collect=dependencies --project-dir=./advi --loops="loop-height=0,total-time>2" -- ./bin/myApplication