Workshop Performance

Modelling and Jmeter

Users vs request

• ¿cuánto aguanta nuestra plataforma?

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

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.

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.

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

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

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

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

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

RUN TEST: the load simulation must reflect the test design

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

JMeter

Modelización y Jmeter

Jmeter Test Plan

User Defined Variables

Functional Test Mode

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

User Behaviour in JMeterOnly Once Controllers

Cache Management

Cookie Management

Header Manager

Think Times

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