Difference between revisions of "GPU621 Team Tsubame"
Yanhao Lei (talk | contribs) (Created page with "= Intel Advisor = == Team Member == # [mailto:ylei11@myseneca.ca?subject=gpu621_project Yanhao Lei] == Progress ==") |
Yanhao Lei (talk | contribs) (→Intel Advisor) |
||
| Line 4: | Line 4: | ||
== Progress == | == Progress == | ||
| + | == Notes == | ||
| + | === What is Intel Advisor? === | ||
| + | The Intel Advisor package provides threading advisor and vectorization advisor to assist programmers in finding the possible parallel enhancements in their serial applications written in C, C++, or FORTRAN. | ||
| + | |||
| + | === How does it work? === | ||
| + | ==== Vectorization Workflow: ==== | ||
| + | Advisor surveys the given binary of an application built in release mode and its source code to determine information such as the time spent processing the instructions in the call stack, the loops that can be vectorized, and the estimates on the merits of vectorizing un-vectorized and under-vectorized loops. You can upgrade the Survey Report to allow it to make better suggestions by collecting additional information through running a Trip Count Analysis to determine the number of times loops and functions are executed; this step is optional. A second run of the Survey Analysis is required after changes are made to the application based on the suggestions in the first Survey Report. If the new report states all loops are vectorized, then the Advisor has completed its job; but this is often not the case in complex programs due to dependencies and memory issues. To resolve these issues, you can mark suspicious sections of the code and use the Dependencies analysis and the Memory Access Patterns (MAP) analysis to identify the causes and make the appropriate changes. | ||
| + | |||
| + | ==== Threading Workflow: ==== | ||
| + | The Threading Workflow also begins with a survey for times and an optional count of invocations to generate the Survey Report. You must add annotations to the source code to identify the sections for the Advisor to try parallelization. With annotations added, Advisor can determine whether the annotated areas are suitable for parallelization and give estimates of the performance boost if the areas are parallelized. Lastly, a Dependencies analysis can identify the data sharing issues within annotated code sections. Similar to the Vectorization Workflow, you can modify the source code and repeat these analyses as necessary to parallelize a serial application. | ||
| + | |||
| + | === How is it actually used? === | ||
| + | The following walk-through assume that you have Visual Studio 2015 and Intel Advisor 2017 installed. | ||
| + | |||
| + | ==== Preparations: ==== | ||
| + | 1. Download and unzip Prefix Scan.zip to a preferred location and open it with Visual Studio 2015. | ||
| + | 2. Set the Balanced Tree project as StartUp Project. | ||
| + | [[File:S1-2.png]] | ||
| + | 3. | ||
Revision as of 03:43, 21 November 2016
Contents
Intel Advisor
Team Member
Progress
Notes
What is Intel Advisor?
The Intel Advisor package provides threading advisor and vectorization advisor to assist programmers in finding the possible parallel enhancements in their serial applications written in C, C++, or FORTRAN.
How does it work?
Vectorization Workflow:
Advisor surveys the given binary of an application built in release mode and its source code to determine information such as the time spent processing the instructions in the call stack, the loops that can be vectorized, and the estimates on the merits of vectorizing un-vectorized and under-vectorized loops. You can upgrade the Survey Report to allow it to make better suggestions by collecting additional information through running a Trip Count Analysis to determine the number of times loops and functions are executed; this step is optional. A second run of the Survey Analysis is required after changes are made to the application based on the suggestions in the first Survey Report. If the new report states all loops are vectorized, then the Advisor has completed its job; but this is often not the case in complex programs due to dependencies and memory issues. To resolve these issues, you can mark suspicious sections of the code and use the Dependencies analysis and the Memory Access Patterns (MAP) analysis to identify the causes and make the appropriate changes.
Threading Workflow:
The Threading Workflow also begins with a survey for times and an optional count of invocations to generate the Survey Report. You must add annotations to the source code to identify the sections for the Advisor to try parallelization. With annotations added, Advisor can determine whether the annotated areas are suitable for parallelization and give estimates of the performance boost if the areas are parallelized. Lastly, a Dependencies analysis can identify the data sharing issues within annotated code sections. Similar to the Vectorization Workflow, you can modify the source code and repeat these analyses as necessary to parallelize a serial application.
How is it actually used?
The following walk-through assume that you have Visual Studio 2015 and Intel Advisor 2017 installed.
Preparations:
1. Download and unzip Prefix Scan.zip to a preferred location and open it with Visual Studio 2015. 2. Set the Balanced Tree project as StartUp Project. File:S1-2.png 3.
