|
|
| (36 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | | + | [https://wiki.cdot.senecacollege.ca/wiki/DPS921_Team_1 Please go to this page title] |
| − | == What is VTune Amplifier? ==
| |
| − | | |
| − | | |
| − | | |
| − | == Where can you get it? ==
| |
| − | | |
| − | | |
| − | | |
| − | == Getting Started ==
| |
| − | | |
| − | | |
| − | | |
| − | == VTune Tutorial 1: Finding HotSpot ==
| |
| − | [[File:1.png|400px]]
| |
| − | | |
| − | This example program will be downloaded when you install VTune Amplifier. Following is the directory that contain the sample code from Intel.
| |
| − | [Program Files]\IntelSWTools\VTune Amplifier XE <version>\sample
| |
| − | Open the project using Visual Studio. Then you can run the the VTune Amplifier and click new Analysis. (You need to download Vtune Amplifier to have that tab on Visual Studio)
| |
| − | <br />
| |
| − | | |
| − | [[File:Tim Hotspt 2.png|400px]]
| |
| − | | |
| − | This should be the next page you will get. You begin to choose different type of Analysis here. We are going do a Basic Hotpots Analysis.Then click start to start the Analysis.
| |
| − | <br />
| |
| − | | |
| − | [[File:Tim Hotspt 3.png|400px]] | |
| − | | |
| − | The program should run itself after you begin.You will notice that the image is loading from the bottom to the top. After the program finish running, it will take a while for Amplifer to generate report.
| |
| − | <br />
| |
| − | | |
| − | [[File:Tim Hotspt 4.png|400px]]
| |
| − | | |
| − | After the program finish running, it will take a while for Amplifer to generate report.
| |
| − | <br />
| |
| − | | |
| − | [[File:Tim Hotspt 5.png|400px]]
| |
| − | | |
| − | The first page will shows a summary of the program.The time it took, the top hotspots, CPU usage etc. We will focus looking at the Hotspots table. we notice that the "initialize_2D_buffer" use the most the CPU time. If you look at the code on ''find_hotspots.cpp'' you will notice it is actually one function in side that cpp file
| |
| − | <br />
| |
| − | | |
| − | [[File:Tim Hotspt 7.png|400px]]
| |
| − | | |
| − | We go to the bootom up tab. it will give you a graph that shows the Hotspots table you got. You can clearly see that "initialize_2D_buffer" use the most time compare to the other function.
| |
| − | <br />
| |
| − | | |
| − | [[File:Tim Hotspt 8.png|400px]]
| |
| − | | |
| − | If we double click on this function we it will shows the sources code and shows you which line of the code actually use the most time in the specific function. Now we can tell that most of the time are spend on the while loop.
| |
| − | <br />
| |
| − | | |
| − | [[File:Tim Hotspt 9.png|400px]]
| |
| − | | |
| − | To compare a paralleled version of this code I already have a program that use CILK PLUS to parallelize that program. Below is the link to download that code. Simply replace the ''find_hotspots.cpp'' with this code, build it and run the Analysis again.
| |
| − | | |
| − | Link:[[File:Find hotspots.zip]]
| |
| − | <br />
| |
| − | | |
| − | | |
| − | [[File:Tim Hotspt 10.png|400px]]
| |
| − | | |
| − | When you run the Analysis this time you will see the program image load at the same time in different level instead of loading from the bottom to the top.
| |
| − | <br />
| |
| − | | |
| − | | |
| − | [[File:Tim Hotspt 11.png|400px]]
| |
| − | | |
| − | This time we should able to see that the Elased Time is shorter than the old time about 10second and the Top Hotspot is no longer "initialize_2D_buffer".
| |
| − | <br />
| |
| − | | |
| − | | |
| − | [[File:Tim Hotspt 12.png|400px]]
| |
| − | | |
| − | If we go to bottom up tab you can see that the "initialize_2D_buffer" is no longer exist and it shows the Cilk worker graph that shows the program is not run a parallel.
| |
| − | <br />
| |
| − | | |
| − | == VTune Tutorial 2: Locks and Wait Tutorial ==
| |
| − | | |
| − | '''1. Prepare for Analysis'''
| |
| − | | |
| − | Note: configuration step is skipped and using default application configuration.
| |
| − | | |
| − | Determine the baseline (total execution time which you will compare subsequent runs of the application).
| |
| − | | |
| − | Do this by running the application for the first time.
| |
| − | | |
| − | After running the application, the baseline for the first run is 6.063s.
| |
| − | | |
| − | [[File:1.PNG]]
| |
| − | | |
| − | == VTune Tutorial 3: Disk input Output Analysis ==
| |
| − | | |
| − | | |
| − | | |
| − | == Resources ==
| |
