38
Performance Modelling Matemáticas y sentido común

After test Barcelona 20160303

Embed Size (px)

Citation preview

Page 1: After test Barcelona 20160303

Performance ModellingMatemáticas y sentido común

Page 2: After test Barcelona 20160303

import randomimport timeimport requests

class Speaker(object):

def __init__(self): born = "Avilés - Asturias" studies = "Applied Maths and Computability" jobdescription = "Performance Jedi" company = "Telefónica I+D" team = "Product Engineering" project = "AWAZZA" talks = [VLC Testing, DevopsDays, WebPerfDays, Velocity]

def talk(self): start_timer = time.time() r = requests.get('http://www.slideshare.net/almudenavivanco') r.raw.read() latency = time.time() - start_timer self.custom_timers[‘After Test 2016'] = latency

if __name__ == '__main__': speech = Speaker() speech.talk() print trans.custom_timers

Almudena Vivanco (@MrsDaehin)

Page 3: After test Barcelona 20160303

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

Page 4: After test Barcelona 20160303

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

Page 5: After test Barcelona 20160303

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.

Page 6: After test Barcelona 20160303

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.

Page 7: After test Barcelona 20160303

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

Page 8: After test Barcelona 20160303

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

Page 9: After test Barcelona 20160303

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

Page 10: After test Barcelona 20160303

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

Page 11: After test Barcelona 20160303

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

Page 12: After test Barcelona 20160303

RUN TEST: the load simulation must reflect the test design

Page 13: After test Barcelona 20160303

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

Page 14: After test Barcelona 20160303

The Maths behind

 

Page 15: After test Barcelona 20160303

“mi tiempo medio de respuesta está bien."

  

Page 16: After test Barcelona 20160303

Afterwards … in PROD ...

Page 17: After test Barcelona 20160303

PerformanceIt's not just about adding more

servers

Page 18: After test Barcelona 20160303

Apdex Indext = acceptable response timesatisfied = response time < t

tolerating = t < response time > 4tfrustrated = response time > 4t

Apdex [t] = (satisfied + tolerating/2)/total requests

Page 19: After test Barcelona 20160303

• Percentiles• Moda• Media• Mediana• Desviación Estándar

• https://msdn.microsoft.com/en-us/library/bb924370.aspx

Page 20: After test Barcelona 20160303
Page 21: After test Barcelona 20160303

Matemáticas y Sentido Común

http://www.raosoft.com/samplesize.html

Page 22: After test Barcelona 20160303
Page 23: After test Barcelona 20160303
Page 24: After test Barcelona 20160303
Page 25: After test Barcelona 20160303
Page 26: After test Barcelona 20160303
Page 27: After test Barcelona 20160303
Page 28: After test Barcelona 20160303

Distribución de Poisson

Page 29: After test Barcelona 20160303

Modelando el uso de la aplicación

Identificar el objetivo de la prueba• Volumen de tráfico?• Escala?• Picos de carga?• Robusto?

Page 30: After test Barcelona 20160303
Page 31: After test Barcelona 20160303

EstadísticasSesiónPáginas VistasFlujoDispositivoLocalizacion

Page 32: After test Barcelona 20160303

Modelización y Jmeter

JMeter

Page 33: After test Barcelona 20160303
Page 34: After test Barcelona 20160303

Jmeter Test Plan

User Defined Variables

Functional Test Mode

Page 35: After test Barcelona 20160303

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

Page 36: After test Barcelona 20160303

User Behaviour in JMeterOnly Once Controllers

Cache Management

Cookie Management

Header Manager

Think Times

Page 37: After test Barcelona 20160303

Jmeter in Cloud commercial tools

Page 38: After test Barcelona 20160303

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

• https://msdn.microsoft.com/en-us/library/bb924370.aspx

• http://www.quotium.com/performance/load-testing-calculating-pacing-time/