Open main menu

CDOT Wiki β

Changes

GPU621/VTuners

1 byte removed, 15:07, 27 November 2022
Algorithm Optimization
== Algorithm Optimization ==
 
[[File:Flame Graph.png|600px|frame|Flame Graph: This is an example of a flame graph selecting the “hottest” processes run in an application which represent 93.3% of the total CPU usage time]]
[[File:Hotspot Analysis.png|600px|frame|Vtune Summary: Here we can see the summary of the output of the Vtune Profiler which shows some general information about the run time and thread usage]]
=== Analyzing Hot Code Paths ===
==== Flame Graphs ====
 
[[File:Flame Graph.png|600px|frame|Flame Graph: This is an example of a flame graph selecting the “hottest” processes run in an application which represent 93.3% of the total CPU usage time]]
The Intel Vtune Profiler provides flame graphs to display a representation of stacks and stack frames in an application. All functions in an application are plotted on a graph and the associated stack depth is represented as height on the y-axis and the width of the bar represents the amount of CPU usage time. The “hottest” functions in an application are then the widest parts on the flame graph.
=== Analyzing Hot Spots ===
 
The Hotspot analysis feature in the Intel Vtune Profiler allows you to dig deeper into your application and identify pieces of code which are taking a long time to execute. These hot spots can be used to identify problem areas in your application and help improve performance.
==== Hotspot Analysis ====
[[File:The Hotspot Analysis.png|600px|frame|Vtune Summary: Here we can see the summary of the output of analysis feature in the Intel Vtune Profiler allows you to dig deeper into your application and identify pieces of code which shows some general information about the run are taking a long time to execute. These hot spots can be used to identify problem areas in your application and thread usage]]help improve performance.
== Microarchitecture and Memory Bottlenecks ==
117
edits