The document covers performance testing, emphasizing its non-functional nature and importance in the software development lifecycle. It outlines when to perform testing, specific methodologies (like load, scalability, and stress tests), and requirements for a successful performance testing environment, including code readiness and realistic target setting. The document also stresses the significance of monitoring and analyzing results to ensure optimal application performance.

1. PERFORMANCE
TESTING
Lee Miguel López
Performance Testing Engineer
milopez@belatrixsf.com
@milopez_ch

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. 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. Why to do Performance Testing

8. Talking about seconds...
15
4
Simple
Conversational
interaction
Short time
Memory
2
Emotionally
committed
Remember
Information
2 sub
Intensive work
ms
Instantaneous

9. Performance Testing Standards
- What I want && What I need.
- But…
Application Performance
Management
- There ARE NOT standards.

11. 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)

12. 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”

13. Inside the project

14. What do I need?
1. Make sure your code is ready and code freeze.
2. Design Performance Test Environment

15. Environment: Expectation

16. Environment: Reality

17. Performance Test Architecture

18. 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.

19. 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

20. Scripting

21. 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.

22. Running Tests

23. Types of Performance Testing

24. Load Test
- Am I ok or not?
- Simulate expected
conditions.
- Important/Critical
transactions.
- Overall performance.
- SLA defined by owner.

25. Scalability Test
- How much can I grow?
- Same app, same env.
- Future expectations.
- Max acceptable level.
- SLA could be changed.

26. Soak Test
- Is memory fine?
- Load test during long time.
- Memory starvation.
- Garbage collector.
- Could take hours, days or
even weeks.

27. Stress Test
- Where am I weak?
- Unexpected conditions.
- Extreme load.
- Modified scripts.
- Find break points.
- Vital for some scenarios.

28. Other kinds
PROFILING
BASELINE
DEBUG

29. 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.

30. Analysis and Monitoring
QUEST SQL

31. 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.

32. Q & A

33. PERFORMANCE
TESTING
Lee Miguel López
Performance Testing Engineer
milopez@belatrixsf.com
@milopez_ch