

To analyze memory usage with the Memory Usage tool, you need to take at least one memory snapshot. If you need to use debugger features while checking memory, such as stepping through code, the debugger-integrated Memory usage tool is recommended.
#Cudalaunch visual profiler code#
For example, if you step through code (F10, F11), PerfTips show you the app runtime duration from the previous step operation to the current step.ĭouble-click on a function that you are interested in, and you will see a more detailed three-pane "butterfly" view, with the selected function in the middle of the window, the calling function on the left, and called functions on the right. You can check information such as the duration of the event (measured from when the debugger was last paused, or when the app started). Using PerfTips, you can view performance information while interacting with your code.

Often, the easiest way to view performance information is to use PerfTips. You can also use the command-line profiler to enable scenarios involving multiple profiling tools. Tools such as CPU Usage may provide complementary data that you can use to help in your analysis. In some scenarios, the window allows you to select multiple profiling tools. To see profiling tool support for different app types, see Which tool should I use? Tools available in the Performance Profiler include: the debugger-integrated tools, see Run profiling tools with or without the debugger. For more information on using the CPU Usage or Memory usage tool in the Performance Profiler vs.
