Scott Barber. Improving System Performance. through a Few Minutes, Every Day, from Everyone

Transcription

1 Improving System Performance through a Few Minutes, Every Day, from Everyone Created for: Let s Test 2013 Runö Conference Centre Åkersberga, Stockholm, Sweden By: Scott Barber Chief Technologist PerfTestPlus, Inc.

2 Chief Technologist, PerfTestPlus, Inc. Co-Founder: Workshop On Performance and Reliability Author: Co-Author: Contributing Author: Books: About me: about.me/scott.barber

3 What is Performance? System or application characteristics related to: Speed: - responsiveness - user experience Scalability: - capacity - load - volume Stability: - consistency - reliability - stress

4 What is a Performant System? A system optimized to balance: Cost Time to Market Capacity while remaining focused on: Quality of Service to System Users

5 Performance vs. Load Testing?

6 The Performance Lifecycle is: Conception to Headstone Not Cradle to Grave

7 Prevent Poor Performance don t just react when it happens.

8 Who is Responsible?

9

10 But where does it fit in the SDLC?

11 Or maybe like this?

12 Or this? Current Capacity Projections Scalability Plan Reliability DevOps & Architects ArchitectsA nalysts & Scrum Single User Responsiveness Resource Management Component-Level Concurrency Prod Dev Stage Test Prepare for Prod Tune/Optimize Predict Early Warning Identification Load Team & DevOps Scrum & Load Team Multi-User Responsiveness Resource Trending Limit Identification

13 Or maybe even?

14 Performant Application Delivery

15 Delivering Performant Systems; Commonly, Y2K -> Today SPE (Software Performance Engineering) Math-centric Architect/Design method + Profiling Context-free code optimization + Load Testing Demonstrate (too late) poor performance characteristics + Capacity Planning Math-centric guessing to determine hardware needs + APM (Application Performance Management) Proactively react to production issues => Inefficient & Reactionary Delivery & Maintenance

16 Delivering Performant Systems; Moving Forward Minimize Need for Complex Mathematics Few teams have mathematicians w/ advanced degrees Disconnect Accuracy from Empirical Production Data Because we can t depend on what we don t have yet Remove Socio-Political Barriers Collaboration improves information sharing & efficiency Keep/Adapt most Valuable Practices Many good concepts have been poorly implemented Distribute Valuable Practices Throughout Life Cycle Many valuable practices have suffered from stove-piping I m testing a model for the entire Performance Journey

17 Performant Application Delivery

18 Key Points Entire Lifecycle Entire Team Focused Individual, Role, & Team Accountability & Responsibility Continuous & Collaborative DevOps Perf Team Individual Code Profiling Requirements Revision Design Validation Budgets Units & Components Monitoring Tuning Load/Stress Testing Environment Config Capacity Planning Concurrency Checks Situation Analysis Snapshots Comparisons Niche Concerns Mini-Field Studies (UAT) What-if

19 Preventing Poor Performance with a little work every day from every one.

20 Proactive Micro & Macro Establish Goals Update Targets Units Stories Tiers Resources Goals Dev & Prod Times Resources Sizes Frequencies Dashboard! Assess Compare Investigate Accept Answer

21

22

23

24 Unit-Level Testing Tools ( cause folks always ask) FireBenchmarks; Performance testing addin for NUnit JUnitPerf; a collection of JUnit test decorators for performance Firefox Performance Tester's Pack HTTPerf

25

26 An Ounce of Prevention

27

28

29 What is it? Load Tests Stress Tests Endurance Tests Infrastructure/Configuration Verification Load Variability Analysis Background Load for Acceptance Tests Or any other deliberate approximation of Production Conditions

30

31

32 Clarify the question Understand the driver(s) behind the question Simplest path to (partial) answer(s) Comprehensive path to (partial) answer(s) Only tasks that fit in time box Stick to tasks requiring available resources Snapshots are your friends Anecdotal is sufficient Identify patterns Confirm patterns (time permitting) Answer(s) Time/Effort to answer(s) Follow-on questions of interest

33

34

35

36 The Bottom Line

37 Addendum

38 Questions?

39 Contact Info about.me/scott.barber Chief Technologist PerfTestPlus, Inc. Web Site: Blog: scott-barber.blogspot.com