Recommended
More Related Content
Similar to Performance testing its not that scary
Similar to Performance testing its not that scary (20)
Recently uploaded
Recently uploaded (20)
Performance testing its not that scary
- 1. Performance Testing its not that Scary! Stephen Mounsey
- 7. Real World Performance Examples • Obama Care 4.7 million people in 24 hours • M&S re-launch 8.1% • According to Google, an extra 500MS of latency costs them 20% of their search traffic
- 8. Performance is important • Google rankings • Mobile – more sensitive • User experience • Conversion rates • Money
- 9. Amazon report a 1% increase in revenue for Every 100ms of Improvement
- 12. Load Load
- 15. Early and Often • How can we do it earlier, smaller units, complete system earlier can you stub or virtualize • Title: Performance Testing its not that scary • We all need to do it – Everyone is responsible for Quality
- 17. • Repeatability – Change – Trends • Realistic – TVM – Concurrency Principles
- 18. • Understand
- 19. Scientific
- 20. Performance Tools • Loadrunner Performance Center • Jmeter • Grinder • Smart Bear • Gatling • MS Load Test • Neo-load • WebLoad • Rational
- 21. • Skills • Products • Technology culture • Support vs Business Critical • Cost • Wider dev integration Tools Selection
- 22. • It’s tough • PT: It’s not that scary • Make your own Recruitment
- 23. What do we do? What do we do?
- 24. Monitoring vs Testing • What if we didn’t performance test? • Pre production is it the same as production? • Always on performance
- 25. • Do you test in production? • Are you outsourcing your perf testing to users • Performance Testing its not that scary! Testing In Production
- 26. A Little about me @stephenmounsey
Editor's Notes
- Description: An interactive talk about why performance testing isn't that scary, key messages being we should all be doing performance testing, why performance is scary and really important and increasingly so. Packed with take home practical advice; key performance terminology discussed and principles and practices which can and should be applied to any performance test, tools and tool selection, recruitment and more. Also discussing why and how we need to change how we performance test with regards agile, dev ops and continuous delivery. Intro – Performance is scary What is Performance Testing and what do the terms mean Principles and Practices which apply to any performance test Tools and tool selection Recruitment – How to find a good performance tester What we do and what we are thinking about. Monitoring vs Testing and Performance in production.
- New Pic
- How many fo you have had a real world performance problem Is it easy to diagnose and fix – was it one or two lines of code
- Amazon – Shopping basket faster payment – less time to think Delivery – Drones (Faster) UK delivery network Walmart increased conversions by 2% for every second of load time improvement
- Ask the audience what terms they use?????? Language is important
- Load vs Performance To do performance testing you need to load the system
- Have you ever felt like there is too much stuff coming at you. With agile, Dev Ops and continuous delivery we cant do perf test in the same way. Mentality Change More PT is required Why did we leave it to the last minute anyway? It has the ability to completely ruin a project
- Start thinking about performance testing in a different way this is no longer something which happens after an app is pretty much complete Change Mentality from a last record and playback test to an early performance engineering approach Continuous – Environment challenges V model
- Repeatability As we are benchmarking – Performance regression we need to be very aware of how repeatable our testing is. Caching – artificially quickly Cleardowns Data – Keep same Network traffic – Jobs Time of Day Realistic to the environment – 1/10 CPU Live Like Data – Obfuscation, Anonamise tools Tests – Live functions Live volumes Changing one thing Scientific thing – only change the thing which you are trying to test Monitor – Vauxhall Corsa vs Nissan GTR
- Understand: Monitor Measure Interoperability
- Ask Audience what they use?
- People are reluctant – Niche Build your own
- Scott Barber Simon Knight Mark Tomlinson James Pulley