Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Performance testing presentation

3,959 views

Published on

Enterprise software needs to be faster than the competition.
In this presentation we will explore what is performance testing, why it is important and when should you implement these tests.

Published in: Software
  • Be the first to comment

Performance testing presentation

  1. 1. PERFORMANCE TESTING Lee Miguel López Performance Testing Engineer milopez@belatrixsf.com @milopez_ch
  2. 2. Walkthrough 1. What is 2. Why is 3. When is recommended 4. What can I do 5. Inside the project 6. What do I need
  3. 3. What is Performance Testing - Non Functional test. - Application + Environment. - Different kind of test. - Vital part of software development life cycle. - Performing well? => Perception. - System perf. = Σ Modules perf.
  4. 4. Why to do Performance Testing
  5. 5. Talking about seconds... 15 4 Simple Conversational interaction Short time Memory 2 Emotionally committed Remember Information 2 sub Intensive work ms Instantaneous
  6. 6. Performance Testing Standards - What I want && What I need. - But… Application Performance Management - There ARE NOT standards.
  7. 7. When is recommended 1. Application with concurrent users. (dah!) 2. Response Time > Critical. 3. Distributed architecture. 4. Shared infrastructure or components. 5. New version or releases. 6. Before sale campaigns. (e-commerces)
  8. 8. What can I do? Replicate: HTTP, FTP, TCP, JDBC, MongoDB, JMS, WS, LDAP, OS, SSH, … … … ISO 8583 Monitoring environment. Export and correlate results. Analysis and diagnosis. “Tell me which protocol are you made of. And I will test you”
  9. 9. Inside the project
  10. 10. What do I need? 1. Make sure your code is ready and code freeze. 2. Design Performance Test Environment
  11. 11. Environment: Expectation
  12. 12. Environment: Reality
  13. 13. Performance Test Architecture
  14. 14. What do I need? 1. Make sure your code is ready and code freeze. 2. Design Performance Test Environment. 3. Setting “Realistic” performance targets. 4. Define and create scripts to emulate transactions.
  15. 15. Scripting - Think Time (simple, random, gaussian) - Delays (uniform, synchronized) - Conditional (simple, double, multip.) - Loop (switch, while, throughput ) - Assertions (http code, text, time) - Managers (cache, cookies, sessions) - Regex
  16. 16. Scripting
  17. 17. What do I need? 1. Make sure your code is ready and code freeze. 2. Design Performance Test Environment. 3. Setting “Realistic” performance targets. 4. Define and create scripts to emulate transactions. 5. Test Data (RIP Performance Testing) 6. Running test.
  18. 18. Running Tests
  19. 19. Types of Performance Testing
  20. 20. Load Test - Am I ok or not? - Simulate expected conditions. - Important/Critical transactions. - Overall performance. - SLA defined by owner.
  21. 21. Scalability Test - How much can I grow? - Same app, same env. - Future expectations. - Max acceptable level. - SLA could be changed.
  22. 22. Soak Test - Is memory fine? - Load test during long time. - Memory starvation. - Garbage collector. - Could take hours, days or even weeks.
  23. 23. Stress Test - Where am I weak? - Unexpected conditions. - Extreme load. - Modified scripts. - Find break points. - Vital for some scenarios.
  24. 24. Other kinds PROFILING BASELINE DEBUG
  25. 25. What do I need? 1. Make sure your code is ready and code freeze. 2. Design Performance Test Environment. 3. Setting “Realistic” performance targets. 4. Define and create scripts to emulate transactions. 5. Test Data (RIP Performance Testing) 6. Run Test and Monitoring. 7. Interpreting results.
  26. 26. Analysis and Monitoring QUEST SQL
  27. 27. What do I need? 1. Make sure your code is ready and code freeze. 2. Design Performance Test Environment. 3. Setting “Realistic” performance targets. 4. Define and create scripts to emulate transactions. 5. Test Data (RIP Performance Testing) 6. Run Test and Monitoring. 7. Interpreting results. 8. Summary.
  28. 28. Q & A
  29. 29. PERFORMANCE TESTING Lee Miguel López Performance Testing Engineer milopez@belatrixsf.com @milopez_ch

×