Performance Continuous Integration

Telefónica Digital

TELEFÓNICA DIGITAL

Barcelona, March 21st 2013

Telefónica DigitalProduct Development & Innovation

About: me

last 8 years i have been working as performance test engineer with different tools and enviroments.

2

Architecture DesignWeb Performance Optimization

The Past

No instruments

Users Review

Late or none Performance Testing

No Real User Monitoring

Reactive Performance Tuning

No tools, no performance dashboard, performance is for sysadmins and operators

Releases are costly and it may take several months of work

Manual testing of each release after code freeze

Non functional Requirements are most likely ignored

In production there is no monitoring of the traffic and how it affects the business

Users feedback is usually negative and there is no interaction with developers and designers

Application’s performance affects directly to market’s performance

• Continuous Integration– Functional testing– Automation– Monitoring

The Present

Continuous Integration for functional testing is working already in nightly builds

Automation reduces time to market for the applications

Monitoring the real user behaviour and not just healthcheck of servers

Error and risks management

Tuning and bugfixing

Listening to user feedback

The Future

• Continuous Performance Integration– Performance tests integrated in Jenkins– Automation of the trend reports– Real User Monitoring Real time feedback


SCRUM and PERFORMANCE

20

Pruebas de RendimientoProactive Performance testing for each release. Load tests will discover the flaws and bottlenecks, the application or the systemmay have in production environment

TestingTesting

Conocer el escenario productivo para tomar una buena decisión sobre cómo orientar las pruebas de rendimiento es La hipótesis de partida con más éxito.Conocer el escenario productivo para tomar una buena decisión sobre cómo orientar las pruebas de rendimiento es La hipótesis de partida con más éxito.Conocer el escenario productivo para tomar una buena decisión sobre cómo orientar las pruebas de rendimiento es La hipótesis de partida con más éxito.Conocer el escenario productivo para tomar una buena decisión sobre cómo orientar las pruebas de rendimiento es La hipótesis de partida con más éxito.Conocer el escenario productivo para tomar una buena decisión sobre cómo orientar las pruebas de rendimiento es La hipótesis de partida con más éxito.Conocer el escenario productivo para tomar una buena decisión sobre cómo orientar las pruebas de rendimiento es La hipótesis de partida con más éxito.Conocer el escenario productivo para tomar una buena decisión sobre cómo orientar las pruebas de rendimiento es La hipótesis de partida con más éxito.Conocer el escenario productivo para tomar una buena decisión sobre cómo orientar las pruebas de rendimiento es La hipótesis de partida con más éxito.Conocer el escenario productivo para tomar una buena decisión sobre cómo orientar las pruebas de rendimiento es La hipótesis de partida con más éxito.High availability of the application and the system is the goal of a ready for service status. The application and the systems must be stable , efficient and dimensioned according to the usage.

AvailabilityAvailability

Not only the response time is important, an intelligent use of the resources is needed to grow in the future. Efficiency, understood as capacity to dispose of the system resources to achive an objective, in our case response time and uptime

VelocityVelocity

Being able to grow depending on the necessities of the market, users and new technologies is one of the focus for a performance engineer

ScalabilityScalability

A performance test is easy. It is easy to design non realistic scenarios. It is easy to collect irrelevant data. Even with a good scenario and Appropiate data, it is easy to use and incorrect statistic method to analysis the results. - Alberto Savoia

ScenariosScenarios

One of the most important parts of a good performance test design is to have an appropiate load test environment, as similar as possible to Production at all levels, networking, systems and application architecture.

PreProductionPreProduction

Otro título

EscenariosEscenariosEscenariosEscenariosEscenariosEscenariosEscenariosEscenariosEscenariosEscenarios

To know the production environment is key to take good decisions about how to design a performance test plan. Designing a plan according To real traffic and usage of the platform is key in creating validation criteria

MonitoringMonitoring

Developers, DBA's, QA's, DevOps, product owners ... All the team is part of performance

Performance TeamsPerformance Teams

Otro título

There are many tools available in the market for load testing and monitoring. An effort in evaluating these tools will benefit at long term the Execution of the tests. However, the most important part is how the reports are generated and who is going to interpret them.

ToolsTools

Otro título

Mas puntos

Not only unique users or session times are important. How the users work with the application and the psicology of the them are key to Understand the results and how it affects to business.

Real User MonitoringReal User Monitoring

Keep it simple, use cache wisely, invest in testing and monitoring, create a culture of performance in all the organization

Best PracticesBest Practices

Tuning

Techonology develops at high speed. To bring out the best of our product, business and techonology need to evolve by the hand. Investing in Performance research is crucial to keep up with other internet competitors.

InnovationInnovation


Understand the Project Vision and ContextProject Vision

Project Context

Understand the system

Understand the Project Environment

Understand the Performance Build Schedule

34


Identify Reasons for Testing Performance

Success Criteria• Application performance requirements and goals

• Performance-related targets and thresholds

• Exit criteria (how to know when you are done)

• Key areas of investigation

• Key data to be collected

35


Identify the Value Performance Testing Adds to the ProjectIn general, the types of information that may be valuable to

discuss with the team when preparing a performance-testing strategy for a performance build include:

› The reason for performance testing this delivery

› Prerequisites for strategy execution

› Tools and scripts required

› External resources required

› Risks to accomplishing the strategy

› Data of special interest

› Areas of concern

› Pass/fail criteria

› Completion criteria

› Planned variants on tests

› Load range

› Tasks to accomplish the strategy

36


Configure the Test Environment

Set up isolated networking environment

Procure hardware as similar as possible to production

Coordinate bank of IP’s for IP spoofing

Monitoring tools and operating systems like production

Load generation tools or develop your own

37


Identify and Coordinate Tasks

Work item execution method

Specifically what data will be collected

Specifically how that data will be collected

Who will assist, how, and when

Sequence of work items by priority

38


Execute Task(s)

Keys to Conducting a Performance-Testing Task

• Analyze results immediately and revise the plan accordingly.

• Work closely with the team or sub-team that is most relevant to the task.

• Communicate frequently and openly across the team.

• Record results and significant findings.

• Record other data needed to repeat the test later.

• Revisit performance-testing priorities after no more than two days.

39


Analyze Results and Report

pause periodically to consolidate results

conduct trend analysis

create stakeholder reports,

pair with developers, architects, and administrators to analyze results

40

But … what are you actually doing day by day?


Case of Study

42

Selenium Framework

Selenium Framework

// Set default NetExport preferences profile.setPreference(domain + "netexport.alwaysEnableAutoExport", true);profile.setPreference(domain + "netexport.showPreview", false);profile.setPreference(domain + "netexport.beaconServerURL", "http://localhost/har-db");profile.setPreference(domain + "netexport.autoExportToFile", false);profile.setPreference(domain + "netexport.autoExportToServer", true);profile.setPreference(domain + "netexport.sendToConfirmation", false); //set net export preferences \\showslow directory to save .har files//profile.setPreference(domain + "netexport.autoExportToFile", true);//profile.setPreference(domain + "netexport.defaultLogDir", "C:\\showslow\har\\");

http://localhost/har-db

V1.0 Branch BBranch A

Xms

Xms + 100ms Xms - 50ms

Branches comparison

Performance trends

Documents

Performance Continuous Integration