Quick Tip: VS2008 – Compare Reports Quickly

While investigating a performance problem you may need to collect many Performance Reports and compare them. You can use the Performance Explorer to quickly compare two reports by: Selecting two reports. Right-clicking and choosing ‘Compare Performance Reports…’ The oldest report will be used for the ‘Baseline’ report and the other report will be used for…

1

What code path is allocating the most bytes for a type?

In Visual Studio 2008, we added the ability to quickly determine the most expensive call stack in your application.  In profiler parlance, the “most expensive call stack” is known as the “hot path”.  What do we mean by “expensive”?  “Expensive” is whatever measure you want it to be: number of samples in a function, time…

1

Very Quick Tip: Getting the most out of your screen for viewing call trees

I spend a lot of time in the profiler’s Call Tree view when I use the profiler.  When you are really digging deep into the tree, screen real estate becomes a big issue.  There is one very simple Visual Studio trick that really helps out so you can get more of the call tree on…

1

Quick Tip: "Save Analyzed" for large VSP files

One cool new feature in the Visual Studio 2008 Profiler is the ability to take a large VSP file that has been analyzed once and save the report data into a VSPS file (Visual Studio Profiler Summary files).  Saving the analyzed data has several major benefits: The analyzed data is orders of magnitude smaller than…

1

Performance: Find Application Bottlenecks with Visual Studio Profiler

A couple of members of the profiler team recently wrote an article for msdn magazine, which describes how to use the Visual Studio 2008 profiler to improve the performance of an application. They examined a Mandelbrot fractal drawing program in some detail and isolated and fixed several performance problems in the code, speeding up program execution time approximately…

1