Tip: VS2008 – Finding and Setting Properties (Right-Click)

The Visual Studio Profiler has many properties and options and this tip shows you where to find most of them. Future posts may cover some of the specific properties in more detail.   Performance Session:   Select an existing Performance Session in the Performance Explorer to see properties in the Properties Window. If the Properties…


Tip: VS2008 – Understanding Performance Targets

If you have a solution that contains multiple projects it is important to know what the ‘Targets’ group in the Performance Explorer is used for. The PeopleTrax solution shown on the right has 4 projects, with 3 of them compiling to managed DLLs and 1 compiling to an executable. After running the Performance Wizard to…


Excluding Small Functions From Instrumentation

In Visual Studio 2008, we added a feature to exclude small functions from instrumentation.  A small function is a function that has very few instructions and makes no function calls (i.e. it’s a leaf).  The idea behind this feature is that small functions are unlikely to be significant in the overall profile of your application,…


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…


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…


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…


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…


Articles on new Visual Studio Team System 2008 profiler features

I’ve recently been working on a series of post on my blog about many of the cool new features that we are adding in Visual Studio Team System 2008 (codename Orcas). So I figured that I’d post a quick link here to all the articles that I’ve finished so far. Collecting Performance Counter information with…


S. Somasegar on new profiler features

S. Somasegar the VP of Developer Division has just put up a post on his weblog detailing some new profiler and debugger features up coming in VS 2008. Check out the article here. [ianhu]