1. Required Slide SESSION CODE: WEB315 Web Load Testing with Microsoft Visual Studio 2010 Richard Campbell Co-Founder Strangeloop Networks

2. Richard Campbell • Background • First laid hands on a microcomputer in 1977, it’s been all downhill since then • Spent the last 15 years helping companies scale applications on a variety of platforms • Currently • Co-Founder and Product Evangelist for Strangeloop Networks • Co-Host of .NET Rocks! • Host of RunAs Radio

3. Why Load Test? • All applications break down under load • The question is: How much load? • Application logic breaks down under load • And that leads to logic error messages for your users • Load issues take time to correct • You can’t rush a caching model into your code

4. All I Need Is One Good Script • Start with the most common scenario • What is likely to be the first scenario that is stress-tested in the real world? • Then build a battery of scripts as the need arises • Create scripts based on real problems your real users are having

5. What Tools? • WCat 6.3 • Light-weight, free, no UI, tricky to set up • Visual Studio 2008 Team Edition for Software Testers • The older tool, but good for web testing • Visual Studio 2010 Ultimate • Web load test tools come only in the ultimate edition

6. What Metrics? • Performance • Time To First Byte (TTFB) • How long does it take for the first byte to arrive at the browser? • Time To Last Byte (TTLB) • How long does it takes for the last byte to arrive at the browser? • Total Load Time • How long for everything to arrive at the browser?

7. What Metrics? • Throughput • Active Sessions • Active Users • Concurrent Users • Pages per Second • Transactions per Second

8. What Metrics? • Bandwidth • Payload size • Round Trip Time (RTT) • AppTurns • Each additional request a browser has to make to the server to complete a web page is an AppTurn

9. Server Measurements • Memory • % Committed Bytes, Working Set Size • Processor • % Consumption • ASP.NET • Session Count • Requests/Sec • IIS • Request Queue Length

10. Performance vs. Scale • Load Time vs. Active Users • Performance focuses on lowest load time • Scale focuses on consistent load times regardless of user count • Everything in Cache vs. No more RAM • If its all cached, its super fast • If you run out of memory, nothing is fast

11. Refactoring for Performance • Cache is King • Invalidation paradigm is crucial • Output caching vs. Cache object • VarybyCustom Output caching • SQL Cache Dependencies

12. Evolving Your Application • Discover caching opportunities • Find logical domains • Static resources, authentication • Distribute within the domain

13. Summary • Establish load test regime early • Script the most common scenario • Understand what is important to your users and your application • Performance, throughput, bandwidth • Evolve your application • Create a performance plan • Specialize and distribute

14. Required Slide Track PMs will supply the content for this slide, which will be inserted during the final scrub. Track Resources • ASP.NET – http://www.asp.net/ • Silverlight – http://silverlight/ • Expression – http://www.microsoft.com/expression/ • Internet Explorer – http://www.microsoft.com/windows/internet-explorer/default.aspx

15. Required Slide Resources Learning • Sessions On-Demand & Community • Microsoft Certification & Training Resources www.microsoft.com/teched www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers • http://microsoft.com/technet • http://microsoft.com/msdn

16. Required Slide Complete an evaluation on CommNet and enter to win!

17. Sign up for Tech·Ed 2011 and save $500 starting June 8 – June 31st http://northamerica.msteched.com/registration You can also register at the North America 2011 kiosk located at registrationJoin us in Atlanta next year

18. © 2010 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.

19. Required Slide