We can grab the Intel Advisor from the Intel Developer Zone site. This tool also comes as part of the Intel Parallel Studio suite and compliments the other Intel tools like Intel Vtune Amplifier and Intel Inspector. Go through the installation process, what options to select for Visual Studio integration, and set up your environment variables.
- [Instructor] We can grab the Intel Advisor tool from the Intel Developer Zone at this URL. On this page let's pick select OS and from the drop-down menu let's pick Windows. Then for the addition let's pick Professional Edition for C++. After that let's click download free trial. This will bring us to a form that we must fill out with a valid email address that we have access to. Make sure you put a valid email here since the download link is sent to that email address. After you fill out the form click the submit button.
Then check your email and once you get the download link, click on it. This will bring us to another page where we have two options for downloading. We can either choose the online setup or the offline installer. The difference is the offline installer has a much larger file size. For right now I'm going to click on the online setup. After the setup is done downloading let's locate it in our downloads directory and double-click it to start the installation. Click run on any prompts that come up and also click yes on any prompts that come up.
The Intell Parallel Studio will start extracting files. Now this is going to be our typical installation routine where we click next, next, we accept the end user license agreement and then eventually finish. When an installation menu pops up make sure you click the install to this computer radio button and then click next. Let's then accept the end user license agreement by clicking on this checkbox and then click next. We then get to this prerequisite issue summary. This is telling us that a system reboot is going to be required and if we want to use the Intel C++ Compiler to offload applications we're going to need additional requirements.
So to keep things simple, we're not going to use the Intel C++ Compiler for this course because that can bring up a lot of other unknown issues on your end. For simplicity we're going to stick to the Microsoft Visual Studio Compiler. Click next. Once the license activation page comes up, we don't have a serial number, so we're going to click the evaluate option and then click next. This next page is asking us to send data about how we use Intel products. We don't want to send any information, so let's click on the no button and then click next.
We then get to the installation summary page which tells us all the components that are about to be installed. Let's click install and then the green bar will start filling up. The installation process can take some time. Once the installation finally completes click on the finish button. You can then open up the documentation in the web browser. This will bring up a page to start exploring the possibilities that you can do with the Intel Parallel Studio. You can look at this page in more detail, but for now I'm going to exit out of here. Let's go back to our desktop and find the Intel Advisor.
After the installation finishes for the Intel Advisor let's locate it in our Windows start menu and drag and drop it over to the desktop for easier access. There's two more things we need to do in order to use the Intel Advisor. This right here on the desktop is the stand alone version. We need to set up the Advisor environment by running a batch file. So let's open up our command prompt and let's navigate to the installation directory of the Intel Advisor. This is the installation directory for the Intel Advisor. It will be program files if you're on a 32-bit system.
If we list the contents of this directory we can see this ADVIXE vars batch file. Let's run this. After we run the batch file we get Intel copyright information. This indicates to us that the environment was properly set. Okay, so that's one down, one to go. We now need to get symbols to point to the Microsoft symbol server. This is required so the Intel Advisor can show us the function names of system modules while we are analyzing our demo application. Let's go to the control panel and make sure you have the view by set to small icons and then click on system.
Then click on advanced system settings. Then under the advanced tab, environment variables. Under the system variables section we need to add two new variables. The first is going to be the NT symbol path variable. And for the variable value we're going to have it point to the Microsoft symbol server. So put this line for the variable value. This NT symbol path variable points to the Microsoft symbol server. It will let the Intel Advisor show us the names of the Windows APIs that are called as a result of function calls the application makes.
This way, even without having access to the source code we can still obtain a general idea about what's happening inside the application and the overall application behavior. We will see this in action later on. Next click okay. Then let's add another variable. Click on the new button right here. For the variable name let's put, NT sym cache path. And for the variable value let's put our local directory called sym cache. This folder will be automatically created for us.
Once set click okay. The NT sym cache variable is for caching our downloaded Microsoft symbols locally onto our own machine so that the symbols can load faster and we don't need an internet connection to get to the Microsoft symbol server every time. This saves time when debugging. Once that's done click okay. And then one more time over here, click okay. And then let's exit out of the control panel. Now the Intel Advisor stand alone version and the one that's now inside Visual Studio are both ready to be used.
- Installing Intel Advisor
- Sorting source code
- Integrating Visual Studio and Intel Advisor
- Discovering parallel code
- Adding markers for parallelism
- Predicting parallel behavior
- Predicting data sharing problems
- Adding parallelism with a task handler
- Forecasting performance gains