1 / 14

Performance Testing and SharePoint

Performance Testing and SharePoint. Jeremy Hancock http://blog.ozippy.com @ ozippy “ Time and Energy Matters”. Daily time saved going from 5s to 2s – 10 page loads per day/person. Some real life experiences. Inconsistency Between 5 and 50 seconds to load a page Reliability

keegan
Download Presentation

Performance Testing and SharePoint

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Performance Testing and SharePoint Jeremy Hancockhttp://blog.ozippy.com @ozippy “Time and Energy Matters”

  2. Daily time saved going from 5s to 2s – 10 page loads per day/person

  3. Some real life experiences • Inconsistency • Between 5 and 50 seconds to load a page • Reliability • Memory leaks causing app pool recycles • Load balancer failures under stress • Latency • 30+ seconds to load a page at remote locations • Poor perception • Page ‘blocking’ causing perceived poor performance

  4. What’ the difference?

  5. My approach

  6. Performance Testing and Optimisation Demo

  7. What did we just look at? • Tools • Yslow • Google Page Speed • Fiddler • Developer dashboard • Asynchronous calls • Caching • Page Output • Blob • Custom

  8. Load/Stress Testing • What are we trying to test? • Will the infrastructure ‘break’ under load? • What is the maximum sustained RPS within the target response time?

  9. Requests Per Second (RPS) • A = Total # of users (1000) • B = Estimated % concurrent users (50%) • C = Average # of requests per day (20 * 10 = 200) • D = Peak ratio (x2) • E = Hours in a business day (8) • Requests per day = A * B * C * D • Seconds per day = E * 3600 (seconds per business day) • RPS = Requests per day/Seconds per day • RPS= (1000 x 50% x200x2)/(8x3600) • RPS= 200,000/28,800 = 6.94 http://blogs.technet.com/b/wbaer/archive/2007/07/06/requests-per-second-required-for-sharepoint-products-and-technologies.aspx

  10. Load Testing Demo

  11. Tips • Difference between F5 and clicking a link • Create warm up scripts • Don’t use think time • Keep tests discrete • Visual Studio does NOT execute JavaScript • % of new users

  12. “Don't lower your expectations to meet your performance. Raise your level of performance to meet your expectations. Expect the best of yourself, and then do what is necessary to make it a reality.” Ralph Marston Respect the Time and Energy of your customers. Don’t forget people that have a high latency link. Make the effort to know what to expect and optimise. Give your users a great perception of performance. Question and Answer

  13. Related Links http://blog.ozippy.com/ “Would you like to save users 1,000+ hours per year?”

More Related