Load Testing is Easy, Good Load Testing is Not. Preparation is the Difference.
180 likes | 337 Vues
Load Testing is Easy, Good Load Testing is Not. Preparation is the Difference. Chris Lynn - Safeway, Inc. Dennis Sherman - Safeway, Inc. Disclaimers. There will be no Greek letters in this presentation. This is an INTRODUCTORY starting point, not an all inclusive list of everything.
Load Testing is Easy, Good Load Testing is Not. Preparation is the Difference.
E N D
Presentation Transcript
Load Testing is Easy, Good Load Testing is Not. Preparation is the Difference. Chris Lynn - Safeway, Inc. Dennis Sherman - Safeway, Inc.
Disclaimers • There will be no Greek letters in this presentation. • This is an INTRODUCTORY starting point, not an all inclusive list of everything. • If you are an advanced load tester then this might be therapy for you to see the same problems in other organizations.
Who is the audience? • How many of you have participated in load testing for 1, 3, 5, 10 years? • How many of you have used/use currently LoadRunner, QALoad, eTester, SLAMD, Load Copient, other? • What percentage of projects you have load tested passed all performance and throughput requirements without any rework of the application? (1%, 5%, 10%, 20%) • How Many are Load Testers, Capacity Planners, Other?
How do you feel? • Often surprised (the bad kind) by my production performance when a new application is released? • I am missing something in my testing? • Production performance doesn’t match the performance in testing? • Do you feel lucky, punk?
What is the Purpose of Testing?What do you want to learn? • Performance Evaluation • Performance Tuning • Stress • Stability • Availability Avoid re-work and wasted work
Who Is Involved? Roles/Responsibilities • Test Manager • Load Tester • Application/Business Representatives • Capacity Planner • Server Engineer • Network Engineer
Know The Business Requirements (not “Business Hopes”) • SLA’s • Transaction Response Times • Throughput • Availability Requirements • # real users • Concurrency (application/logged in, application active, transaction)
Define the Scope of Testing • Time • Potential Liklihood of change • Sufficient Load Generation Capacity • Just the online application, or also the batch, reporting, ETL, middleware, annual processing, alternate clients (wireless, time clocks) etc. • LAN/WAN
Test Environment Considerations • Hardware/Platform • Size • Versions • Load Balancing • Network Simulation • Software Infrastructure • Application Functionality • Monitoring Tools
Other Considerations • Usage Patterns • Transaction Mix • Load Generation Limitations • 1000 real users doesn’t always require 1000 VU’s
Test Tracking and Reporting • Test Parameters (repeatability) • Test Results • Throughput • Response times • System impacts
Templates Available • Transaction Mix Identification • Test Plan Creation • Load Generator Identification/Installation/Operation • Initial/Validation Tests • Initial/Validation Report • Primary Load/Performance Tests • Primary Load/Performance Report
Conclusions • Planning Makes All the Difference!!! • Know Why You Are Testing • Understand The Test Environment • Understand The Business/Customer Requirements • Know Who To Involve Test Like The Wind