HELP WHEN YOU NEED IT

Use these resources for assistance with Intel® Advisor.

Ask the Community

Talk with other users and experts in our forum.

Priority Support

All paid versions of Intel® Software Development Products automatically include Priority Support for one year from your date of purchase. You get:

  • Direct and private interaction with Intel’s engineers—submit confidential inquiries and code samples
  • Free access to all new product updates and continued access to, and support for, older versions of the product
  • Responsive help with your technical questions and other product needs for both new and older versions
  • Community product forums followed by expert users of all Intel Software Development Products
  • Access to a vast library of self-help documents that build off of decades of experience with creating high-performance code
  • Extended support at a reduced rate

Paid licenses are available for Intel Parallel Studio XE and Intel System Studio.

If you have more questions, review our Purchase FAQ.

See Who’s Eligible

Priority Support

Priority Support FAQ

How to Submit a Request

Vectorization Advisor

Can I run the Vectorization Advisor on serial and multithreaded binaries?

Yes. Unlike the Threading Advisor, the Vectorization Advisor works out of the box on both serial and multithreaded binaries.

Must I annotate source code to use the Vectorization Advisor?
No. Unlike the Threading Advisor, the Vectorization Advisor does not require source code modification to perform analyses. You can select loops for deeper analysis in the Survey Report. Note: Save time by annotating your code when you run dependencies or memory access patterns analyses on long-running applications. This allows you to skip the survey collection step.
How can I decrease the analysis time?

Survey analysis is not intrusive and does not significantly slow down the application execution. However, the dependencies, memory access patterns (MAP), and other analysis types have significant overhead. There are several ways to mitigate application execution slowdown:

  • Decrease the workload. How you do that depends on your application. For example: provide less data to process, decrease computation complexity, and so on.
  • Use separate Project Properties settings for the survey and other analysis types. By default, it’s enough to configure only the survey analysis settings, but if you can control the workload via command line parameters, you can keep separate command line settings for different analysis types.
  • Decrease the number of selected loops for additional analyses.
  • Watch the Refinement Reports window while the analysis runs. As soon as you see the data you need, in VECTORIZATION WORKFLOW, click Stop.
How are surveys, trip counts, dependencies, and memory access pattern (MAP) analysis results related at the file level?

The Vectorization Advisor has a complex structure of result versions. All the analysis results are saved in an experiment folder named e000. The base analysis type is Survey. All other analysis types depend on the Survey analysis result, but don’t depend on each other. Different analysis types are matched by an address in the target application binary. That means when you select loops in the survey report for deeper analysis (dependencies or MAP), the loops are identified by the address in the binary. Changing the binary (rebuilding) between running the survey, dependencies, and MAP analyses breaks this connection, producing incorrect results. The same applies to trip counts analysis. So if a binary is changed, rerun the survey analysis before running other analysis types.

Threading Advisor

Can I run this feature on serial and multithreaded binaries?

No. Unlike the Vectorization Advisor, which works out of the box for both serial and multithreaded binaries, the Threading Advisor—specifically the suitability analysis and sometimes the dependencies analysis—works only on serial binaries. Note: You can convert a multithreaded OpenMP* binary to a serial binary by recompiling with the qopenmp-stubs option.

Must I annotate source code to use the Threading Advisor?

Yes. Annotations are a quick way for you to provide descriptions of a threading design to the Threading Advisor. They allow the feature to evaluate the design, forecast the performance gain, and highlight any synchronization issues. The good news is that the compiler ignores annotations and doesn't change the code behavior. So you can feel confident you’re not introducing threading errors or invalidating test cases as you explore alternative threading designs while continuing normal development and testing.

Both Vectorization and Threading Advisor

How do I run this application from a command line?

In the WORKFLOW pane, click Command Line to generate the command line for an analysis type and project settings. For additional instructions, see Command Line and Message Passing Interface (MPI).

How do I run the Intel Advisor with a message passing interface (MPI) application?

For instructions, see Command Line and Message Passing Interface (MPI) and the Intel® MPI Library Reference Manual.

How do I save results?

By default, this application stores only the most recent result of any given analysis type in a particular project. This means that rerunning the same analysis type as part of the same project completely replaces the appropriate data, with no ability to recover the old data. To manually save results in a read-only folder that you can browse any time, click Snapshot (the button with a camera image). New snapshots do not overwrite previous snapshots—access them with the Project Navigator.