Performance meetup in Barcelona July 2013

1. Speed me Up!
Performance Testing Best
Practices

3. Goal: performance tests determine system and user
responses, throughput, reliability, scalability of a system under load

4. “Performance test is easy. It is easy to design not realistic scenarios. It is easy to collect irrelevant
data. Even, with a good scenario and good data it is easy to use incorrect statistical Method.” –
Alberto Savoia

5. SCENARIOS: Identify the scenarios that are most commonly executed or most resource-intensive

6. WORKLOAD MODEL: User Session Duration in average. It is important to define the load levels
that will translate into concurrent usage, overslapping users, or user sessions per second.

7. USER SCENARIO: Navigational Path, including intermediate steps or activities, taken by the user
to complete a task. We will call it User Session from now on.

8. THINK TIMES: User thinktimes  Pause between pages during a User Session depending on the
User Type*

9. User Types: Identify the User … new, revisiting… devices, networks…

10. Performance Acceptance Criteria: Response time, System load, Throughput ...

11. METRICS: Only well-selected metrics that are analyzed correctly and contextually provide
information of value.

12. DESIGN TEST: Using your scenarios, key metrics, and workload analysis …

13. RUN TEST: the load simulation must reflect the test design

14. ANALYZE RESULTS: Find bottlenecks, memory leaks, cpu hogs, bad sofware design …

15. Monitor Performance in production: and check if the assumptions from your test phase are
correct. Adapt your tests always to production experience.

16. • http://www.raosoft.com/samplesize.html
• http://analyze.websiteoptimization.com/wso
• http://mobitest.akamai.com/m/index.cgi
• http://stevesouders.com/mobileperf/mobilep
erfbkm.php