2. Vance Morrison Performance Architect Microsoft Corporation

4. L1 CacheL2 CacheMemoryDisk Size64K512K2000M100,000M Access Time.4ns4ns40ns4,000,000ns

7. Select Columns Working Set tends to Overestimates Memory Impact (shared OS files) But does not account for read files. Private Working Set Underestimates Impact Small 100 Meg WS Small 50 Meg Private

9. Adding New Counters

10. 1 Open.NET CLR Memory2 Select Counters4 Add 5 OK3 Select Process

11. Set Display to ReportGC Heap Size So 7.3 Meg of the 8.6 Meg of private working set is the GC Heap % Time in GC ideally less than 10% Ratios of GC Generations Gen0 = 10 x Gen 1, Gen 1 = 10 x Gen 2 % Time in GC

12. 1 Total WS 2 Breakdown 3 DLL Breakdown GC Heap Here Only These Affect Cold Startup

20. Related Sessions Session TitleSpeakerDayTimeLocation PC53 Lunch: Building High Performance JScript AppsSameer Chabungbam Mon 12:45-1:30PM 515B Microsoft Visual Studio: Bringing out the Best in Multicore SystemsHazim ShafiMon 1:45-3:00PM 502A WCF: Zen of Performance and ScaleNicholas AllenTues 12:45-1:30PM 515B SQL Server 2008: Developing Large Scale Web Applications and ServicesJose BlakeleyTues 1:45-3:00PM 411 Using Instrumentation and Diagnostics to Develop High Quality SoftwareRicky BuchTues 5:15-6:30PM 408B TL24 Improving.NET Application Performance and ScalabilitySteve CarolWed 1:15-2:30PM 153 Parallel Programming for Managed Developers with the Next Version of Microsoft Visual Studio Daniel MothWed 10:30-11:45AM Petree Hall HOL CodeTitle TLHOL11VSTS 2010: Diagnostics and Performance Related Labs

21. © 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.