Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
How toHow to
test performancetest performance
and not die tryingand not die trying
Diego Cardozo - Sr. Web Performance Eng...
AgendaAgenda
What to measure
Quick tests
Automation
Selling performance
What to measure (1)What to measure (1)
Types of performance testing for web applications
(According to Microsoft)
Test typ...
What to measure (2)What to measure (2)
3 alternatives to set performance goals
Performance budget
Business-specific measure...
What to measure (3)What to measure (3)
Response time limits - Ph.D Jakob Nielsenn
Time Perseption Action
0 - 16ms Continuo...
Quick testsQuick tests
Use ngrok to run local tests
Utilities and plugins for CI and automation
Chrome's dev tools
Measure...
Automation (1)Automation (1)
First proposal - continuous process
Run performance tests along with functional
automated tes...
Automation (2)Automation (2)
Second proposal - RUM
Performance information is sent directly and
passively from real users
...
Selling performance (1)Selling performance (1)
Present this ideas to your boss/customer
: 2% slower = 2% less searching pe...
Selling performance (2)Selling performance (2)
Generate revenue directly from performance
Performance can be sold as a ser...
ResourcesResources
Slides
RAIL
Microsoft's performance testing guide for web apps
slides.com/diegocard/testeando-performan...
¿Questions?¿Questions?
diegocard@gmail.comdiegocard@gmail.com
Upcoming SlideShare
Loading in …5
×

How to test performance and not die trying

629 views

Published on

Presentation on performance testing @ 3rd testing meetup, LATU (Uruguay's Technological Laboratory).

Agenda:
1. What to measure
2. Quick tests
3. Automation
4. Selling performance

Published in: Software
  • D0WNL0AD FULL ▶ ▶ ▶ ▶ http://1lite.top/d8epH ◀ ◀ ◀ ◀
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

How to test performance and not die trying

  1. 1. How toHow to test performancetest performance and not die tryingand not die trying Diego Cardozo - Sr. Web Performance Engineer NetSuite
  2. 2. AgendaAgenda What to measure Quick tests Automation Selling performance
  3. 3. What to measure (1)What to measure (1) Types of performance testing for web applications (According to Microsoft) Test type Goal Performance Determine speed and scalability Load Determine behavior under normal circumstances Stress Determine behavior beyond normal circumstances Capacity How many users or transactions are supported while meeting performance goals
  4. 4. What to measure (2)What to measure (2) 3 alternatives to set performance goals Performance budget Business-specific measurement like Twitter's "time to first tweet" Google's RAIL model
  5. 5. What to measure (3)What to measure (3) Response time limits - Ph.D Jakob Nielsenn Time Perseption Action 0 - 16ms Continuous Animation 0 - 100ms Immediate Response 100ms - 300ms Slight delay 300ms - 1s Natural progression Load 1s+ User loses focus 10s+ Frustration
  6. 6. Quick testsQuick tests Use ngrok to run local tests Utilities and plugins for CI and automation Chrome's dev tools Measurements can be saved Emulates mobile Web page test Google PageSpeed Insights
  7. 7. Automation (1)Automation (1) First proposal - continuous process Run performance tests along with functional automated tests Works together with performance budget Knowing how performance evolves with time during development is extremely valuable Example: sitespeed.io Keynote
  8. 8. Automation (2)Automation (2) Second proposal - RUM Performance information is sent directly and passively from real users Ideal for mobile apps The testing team can experiment with RUM tools from day one When the site or app goes live you will already have the necessary know how on interpreting results Example: (mobile)HP AppPulse
  9. 9. Selling performance (1)Selling performance (1) Present this ideas to your boss/customer : 2% slower = 2% less searching per user : 400ms faster = 9% more traffic : 100ms faster = 1% more revenue : 5s faster = 25% more page views, 7 to 12% more revenue uses website speed in search rankings Google Yahoo Amazon Shopzilla Google
  10. 10. Selling performance (2)Selling performance (2) Generate revenue directly from performance Performance can be sold as a service or added value Generates revenue which will cover for the cost of paid tools If offered but not sold, it will still help you set expectations and prevent performance-related issues Other alternatives such as performance alerts or paid reports can be sold too
  11. 11. ResourcesResources Slides RAIL Microsoft's performance testing guide for web apps slides.com/diegocard/testeando-performance www.smashingmagazine.com/2015/10/rail-user- centric-model-performance msdn.microsoft.com/en-us/library/bb924375.aspx
  12. 12. ¿Questions?¿Questions? diegocard@gmail.comdiegocard@gmail.com

×