117
edits
Changes
→Top-down Microarchitecture Analysis
= Intel Vtune Profiler =
Intel VTune Profiler, called Intel VTune Amplifier, is an application performance evaluation and analysis tool working in Microsoft Windows or Linux systems. Its features mainly run for Intel and AMD hardware and some are only for Intel-made CPUs or GPUs. There are six main analysis features: Algorithm Optimization, Microarchitecture and Memory Bottlenecks, Accelerators and XPUs, Parallelism, Platform and I/O, and Multi-Node. One can download it for free on the Intel® VTune™ Profiler website as a stand-alone version or as part of the Intel® oneAPI Base Toolkit. However, parts of advanced analysis in some features are paid services.
= Group Members =
[[File:Top-Down Analysis Method.png | frame | 400px | Microarchitecture Exploration Summary: This shows you the different functions utilized throughout the application and their respective performance metrics that tell us the percentage of Front-End Bound and Back-End Memory Bound, and others]]
==== Main Benefits of The Microarchitecture and Memory Modules ====The Intel Vtune Profiler allows you to utilize microarchitecture exploration analysis to improve the performance of your applications by pinpointing issues with hardware. It and is also able to identify memory-access-related problems including cache misses and high-bandwidth problems.
==== Top-down Microarchitecture Analysis ====
The Intel Vtune Profiler includes a tool to conduct a Microarchitecture Exploration analysis using events collected in the top-down characterizationand allows user to pinpoint hardware issues in an application. The Microarchitecture Exploration records other metrics important to performance and are displayed in the Microarchitecture Exploration viewpoint. Using the hotspot analysis from the algorithm optimization section we are able to identify areas in which our code is taking a lot of CPU time to run. This then allows us to pinpoint an area to utilize the ME analysis tool to determine the level of efficiency of the code running through the core pipeline. The Microarchitecture Exploration Summary highlights ME analysis instructs the Vtune Profiler to collect a list of events for us potential areas analysis and determines metrics which could be optimizedallow easier identification of performance issues at the hardware level. === Pinpointing memory-access-related problems ===
== Accelerators and XPUs ==
= Vtune Profiler in Practice =
The following is code we utilized to test out the features of the Vtune Profiler on.
The code is produced by Microsoft and is intended to demonstrate how to convert a basic loop with OpenMP using the Concurrency Runtime algorithm.
}
</pre>
The output of the code is fairly simple and only relays back the number of prime numbers found using the OpenMP and Concurrency Runtime methods and nothing else.
<pre>
Using OpenMP...
found 107254 prime numbers.
Using the Concurrency Runtime...
found 107254 prime numbers.
</pre>
The results of the Vtune Profiler on the above code produces the results below
[[File:Hot Spot Results.png]]
Here we have the Hot Spots in our code and since it is a relatively simple application and we only have one main function that makes up a majority of CPU usage time. If we were to utilize the Vtune Profiler on a more complex application we would definitely see other functions and more interesting results overall.
[[File:Hot Path Results.png]]
This is our Flame Graph here and again since we have a simple application which only ran for 10 seconds there is little to see. What we can see is that we have 3 chunks of CPU usage throughout the lifetime of the application. Our first chunk appears to be the initialization of the code and functions to start the code running. The second chunk shows the Concurrency Runtime algorithm being executing the is_prime function, similarly in the final chunk we see the OMP version of the is_prime function.
==References==
*[https://www.intel.com/content/www/us/en/develop/documentation/vtune-cookbook/top/configuration-recipes/analyzing-hot-code-paths-using-flame-graphs.html Analyzing Hot Code Paths]
*[https://www.intel.com/content/www/us/en/develop/documentation/vtune-help/top/analyze-performance/algorithm-group/basic-hotspots-analysis.html Analyze Hot Spots]
*[https://learn.microsoft.com/en-us/cpp/parallel/concrt/how-to-convert-an-openmp-parallel-for-loop-to-use-the-concurrency-runtime?view=msvc-170 How to: Convert an OpenMP parallel for Loop to Use the Concurrency Runtime]
