1. Workshop Performance
Modelling and Jmeter

2. Users vs request
• ¿cuánto aguanta nuestra plataforma?

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

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

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

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

7. User Types: Identify the User … new, revisiting or both.

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

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

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

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

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

13. JMeter
Modelización y Jmeter

17. Jmeter Test Plan
User Defined Variables
Functional Test Mode

18. User defined Variables at Test Plan level to be used from Jenkins

19. User Behaviour in JMeter
Only Once Controllers
Cache Management
Cookie Management
Header Manager
Think Times

20. Resources
• http://www.raosoft.com/samplesize.html
• http://analyze.websiteoptimization.com/wso
• http://mobitest.akamai.com/m/index.cgi
• http://stevesouders.com/mobileperf/mobileperfbkm.php
• http://play.tid.es/M5/2.0/1/an/BR/
• http://enjoy.tid.es/tools/simulator/2.0/enjoyUNIAPIclient.p
hp