Performance Testing and SharePoint<br />Jeremy Hancockhttp://blog.ozippy.com<br />@ozippy<br />“Time and Energy Matters”<b...
Daily time saved going from 5s to 2s – 10 page loads per day/person<br />
Some real life experiences<br />Inconsistency<br />Between 5 and 50 seconds to load a page<br />Reliability<br />Memory le...
What’ the difference?<br />
My approach<br />
Demo<br />Performance Testing and Optimisation<br />
What did we just look at?<br />Tools<br />Yslow<br />Google Page Speed<br />Fiddler<br />Developer dashboard<br />Asynchro...
Load/Stress Testing<br />What are we trying to test?<br />Will the infrastructure ‘break’ under load?<br />What is the max...
Requests Per Second (RPS)<br />A = Total # of users (1000)<br />B = Estimated % concurrent users (50%)<br />C = Average # ...
Demo<br />Load Testing<br />
Tips<br />Difference between F5 and clicking a link<br />Create warm up scripts<br />Don’t use think time<br />Keep tests ...
Question and Answer<br /><ul><li>Respect the Time and Energy of your customers.
Don’t forget people that have a high latency link.
Upcoming SlideShare
Loading in …5
×

Performance testing your SharePoint implementation to ensure a great user experience

34,756 views
34,653 views

Published on

What is performance testing and why should you make it a regular part of your SharePoint projects? We will go through a number of techniques and live demonstrations for how to go about performance testing and some of the tools available to work with. We’ll also discuss some of the experiences from the field of what might be wrong and how those issues were identified and addressed.

Published in: Technology, Health & Medicine
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
34,756
On SlideShare
0
From Embeds
0
Number of Embeds
32,760
Actions
Shares
0
Downloads
25
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Performance testing your SharePoint implementation to ensure a great user experience

  1. 1. Performance Testing and SharePoint<br />Jeremy Hancockhttp://blog.ozippy.com<br />@ozippy<br />“Time and Energy Matters”<br />
  2. 2.
  3. 3. Daily time saved going from 5s to 2s – 10 page loads per day/person<br />
  4. 4. Some real life experiences<br />Inconsistency<br />Between 5 and 50 seconds to load a page<br />Reliability<br />Memory leaks causing app pool recycles<br />Load balancer failures under stress<br />Latency<br />30+ seconds to load a page at remote locations<br />Poor perception<br />Page ‘blocking’ causing perceived poor performance<br />
  5. 5. What’ the difference?<br />
  6. 6. My approach<br />
  7. 7. Demo<br />Performance Testing and Optimisation<br />
  8. 8. What did we just look at?<br />Tools<br />Yslow<br />Google Page Speed<br />Fiddler<br />Developer dashboard<br />Asynchronous calls<br />Caching<br />Page Output<br />Blob<br />Custom<br />
  9. 9. Load/Stress Testing<br />What are we trying to test?<br />Will the infrastructure ‘break’ under load?<br />What is the maximum sustained RPS within the target response time?<br />
  10. 10. Requests Per Second (RPS)<br />A = Total # of users (1000)<br />B = Estimated % concurrent users (50%)<br />C = Average # of requests per day (20 * 10 = 200)<br />D = Peak ratio (x2)<br />E = Hours in a business day (8)<br />Requests per day = A * B * C * D<br />Seconds per day = E * 3600 (seconds per business day)<br />RPS = Requests per day/Seconds per day<br />RPS= (1000 x 50% x200x2)/(8x3600)<br />RPS= 200,000/28,800 = 6.94<br />http://blogs.technet.com/b/wbaer/archive/2007/07/06/requests-per-second-required-for-sharepoint-products-and-technologies.aspx<br />
  11. 11. Demo<br />Load Testing<br />
  12. 12. Tips<br />Difference between F5 and clicking a link<br />Create warm up scripts<br />Don’t use think time<br />Keep tests discrete<br />Visual Studio does NOT execute JavaScript<br />% of new users<br />
  13. 13. Question and Answer<br /><ul><li>Respect the Time and Energy of your customers.
  14. 14. Don’t forget people that have a high latency link.
  15. 15. Make the effort to know what to expect and optimise.
  16. 16. Give your users a great perception of performance.</li></ul>“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.”<br />Ralph Marston<br />
  17. 17. Related Links<br />http://blog.ozippy.com/<br />“Would you like to save users 1,000+ hours per year?”<br />

×