Browse by Tags

Tagged Content List
  • Blog Post: 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...
  • Blog Post: 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...
  • Blog Post: 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...
  • Blog Post: 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...
  • Blog Post: 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...
  • Blog Post: 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 the screen at one time without...
  • Blog Post: 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 ( V isual S tudio P rofiler S ummary files). Saving the analyzed data has several major benefits: The analyzed data is orders...
Page 1 of 1 (7 items)