Upload
chamal-asela-perera
View
265
Download
1
Embed Size (px)
Citation preview
Continuous Performance Assessments
With Jenkins, Jmeter and BlazeMeter
By Chamal Asela Perera & Nipuna Madusanka
Speakers
Nipuna Madusanka
https://lk.linkedin.com/in/nipunam
[email protected] https://lk.linkedin.com/in/chamalp
Chamal Asela Perera
The Challenges
• Shorter development cycles require more tests in less time
• ‘Working’ code does not always perform well
• Developer needs feedback
Implementation of Continuous Performance Assessments?• New features – Not new performance
issues?
Our Approach
Performance Trend Analysis…
Importance of Continuous Performance Assessments?
• Avoid late performance problem discovery
• Making changes earlier when they are cheaper
Conception Design Development Testing Release
Cost to Fix a bugX1000
X100
X10
x1
Have we covered everything ? . . . .
The Big Picture
FINAL SPRINTDEPLOYMENT PHASE
Setup Performance Monitoring System
Create Backlog Items for
Identified Issues
Responding to Performance
Alerts
SPRINT NDEVELOPMENT PHASE
Bottleneck Identification
Architecture Assessment
Add Performance Engineering items to Product Backlog
Major Release Assessment
Trend Analyzing and Benchmarking
SPRINT N+1
Prioritization
Implementation
Re-assessment
SPRINT 0INITIAL PHASE
Understand Performance Requirements
Setup Environment & Framework
Create Performance
Strategy
Knowledge transfer between
all the stakeholders
Is this the only way? . . . . . .
Demo• Record JMX through BlazeMeter• Configure Jmeter and Jenksins for the
CPA• Configure Blazemter plugin for Jenkins• Compare the performance of builds