app performance: the windows performance toolkit

16

Upload: clare

Post on 20-Feb-2016

66 views

Category:

Documents


0 download

DESCRIPTION

App Performance: The Windows Performance Toolkit. Chell Sterioff Senior Program Manager 3-100. Agenda. The performance j ourney Windows Performance Toolkit (WPT) Iterative approach to perf a nalysis Demo. Objective. Familiarize you with the tools for a pp a nalysis. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: App Performance:  The Windows Performance Toolkit
Page 2: App Performance:  The Windows Performance Toolkit

App Performance: The Windows Performance Toolkit

Chell SterioffSenior Program Manager3-100

Page 3: App Performance:  The Windows Performance Toolkit

The performance journeyWindows Performance Toolkit (WPT)Iterative approach to perf analysisDemo

Agenda

Page 4: App Performance:  The Windows Performance Toolkit

ObjectiveFamiliarize you with the tools for app analysis

Page 5: App Performance:  The Windows Performance Toolkit

Follow the Performance Journey

Where are we in the performance journey?

ThePerformanceJourney

Design &Plan

Architect &Develop Instrument Test &

Measure Analyze

Design for performance

Deliver consistent performance

Page 6: App Performance:  The Windows Performance Toolkit

Follow the Performance Journey

Where are we in the performance journey?

ThePerformanceJourney

Design &Plan

Architect &Develop Instrument Test &

Measure Analyze

Design for performance

Deliver consistent performance

Page 7: App Performance:  The Windows Performance Toolkit

Performance toolsVisual Studio

Windows Performance Toolkit (WPT)

Page 8: App Performance:  The Windows Performance Toolkit

Windows Performance ToolkitWindows Performance Recorder (WPR)Allows you to capture a trace for the problem you want to investigate

Windows Performance Analyzer (WPA)Exposes information about the system and allows you to do in-depth performance analysis

Page 9: App Performance:  The Windows Performance Toolkit

An iterative approach1. Identify a problem2. Measure the scenario

a) Capture a trace of the problem

3. Analyzea) Determine if you are CPU, disk, or network boundb) Identify UI threadc) Look at where time is being spent

4. Modify app and iterate

Page 10: App Performance:  The Windows Performance Toolkit

An iterative approach1. Identify a problem2. Measure the scenario using WPR

a) Capture a trace of the problem

3. Analyzea) Determine if you are CPU, disk, or network boundb) Identify UI threadc) Look at where time is being spent

4. Modify app and iterate

Page 11: App Performance:  The Windows Performance Toolkit

An iterative approach1. Identify a problem2. Measure the scenario using WPR

a) Capture a trace of the problem

3. Analyze in WPAa) Determine if you are CPU, disk, or network boundb) Identify UI threadc) Look at where time is being spent

4. Modify app and iterate

Page 12: App Performance:  The Windows Performance Toolkit

Capturing a TraceWPA Basics: Identifying Blocking ResourceThe UI ThreadGraphics AnalysisDiffing

Demo

Page 13: App Performance:  The Windows Performance Toolkit

ResourcesPrior Talks:2-098 App performance: planning is cheaper than re-architecting3-099 App performance: scenario based UX design3-097 App performance: the mental model for interacting with the platform

Related Talks:3-316 Developing high performance websites and apps with JavaScript performance tools3-332 Visual Studio 2013 diagnostics tools for XAML-based Windows Store apps

Page 15: App Performance:  The Windows Performance Toolkit

Evaluate this session

Scan this QR code to evaluate this session and be automatically entered in a drawing to win a prize!

Page 16: App Performance:  The Windows Performance Toolkit

© 2012 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.