Walkthroughs: Using VSTS Test and Profilers to Find Performance Issues

Tess Ferrandez recently wrote a couple of articles that extend her popular series of debugging labs to focus on measuring and improving performance. In ‘Using VSTS Test and Profilers to troubleshoot performance issues (low cpu hang)‘, Tess introduces a performance problem into an ASP.NET application and uses the Visual Studio Profiler with a Load Test to track down the problem….

0

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

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

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…

0