Performance Testing [not] somebody I used to know

39
Somebody that I used to know Performance Testing - Gotye Tuesday, 19 February 13

Transcript of Performance Testing [not] somebody I used to know

Page 1: Performance Testing [not] somebody I used to know

Somebody that I used to know

Performance Testing

“- Gotye

Tuesday, 19 February 13

Page 2: Performance Testing [not] somebody I used to know

10,000 hour rule

“The key to success in any field is, to a large extent, a matter of practicing a specific task for a total of around 10,000 hours.

Tuesday, 19 February 13

Page 3: Performance Testing [not] somebody I used to know

about 34 projects multiplied by 3 months each by 20 days per month by 8 hours per day at 20% efficiency

equals ...

My ‘time on the mainframe’

Tuesday, 19 February 13

Page 4: Performance Testing [not] somebody I used to know

Knowledge vs. Time

3,264 hours

K

How much you think you know

How much you actually know

t

Tuesday, 19 February 13

Page 5: Performance Testing [not] somebody I used to know

20% Efficiency?

Tuesday, 19 February 13

Page 6: Performance Testing [not] somebody I used to know

Mostly Effective

Most performance test efforts are effective ...

“Testing was completed”“NFRs were met”“We survived go-live”

Tuesday, 19 February 13

Page 7: Performance Testing [not] somebody I used to know

Rarely Efficient

Performance test efforts are rarely efficient ...

Tuesday, 19 February 13

Page 8: Performance Testing [not] somebody I used to know

Lossiness

(lossy) characterized by or caused by dissipation of energy.

Tuesday, 19 February 13

Page 9: Performance Testing [not] somebody I used to know

Tools

1,000 VU license = enough to feed a village

“We waste a LOT of energy on tools and people to execute the performance test effort.

Tuesday, 19 February 13

Page 10: Performance Testing [not] somebody I used to know

Why so Much?

http://1.bp.blogspot.com/_T3Gqqkz9Mm0/TFEoMfpM6-I/AAAAAAAAB0o/8RslwtCum-4/s1600/tail.jpg

Tools are driving the process!We are suffering from market distortion ...

Tuesday, 19 February 13

Page 11: Performance Testing [not] somebody I used to know

Perfect Competition

http://1.bp.blogspot.com/_T3Gqqkz9Mm0/TFEoMfpM6-I/AAAAAAAAB0o/8RslwtCum-4/s1600/tail.jpg

“Describes markets such that no participants are large enough to have the market power to set the price of a homogeneous product.

Tuesday, 19 February 13

Page 12: Performance Testing [not] somebody I used to know

Imperfectly Competitive

At first there were few sellers and now there are many s e l l e r s w i t h h i g h l y differentiated products ...

Tuesday, 19 February 13

Page 13: Performance Testing [not] somebody I used to know

At first there were few

Tuesday, 19 February 13

Page 14: Performance Testing [not] somebody I used to know

And now there are many

Tuesday, 19 February 13

Page 15: Performance Testing [not] somebody I used to know

Selenium vs. QTP

Tuesday, 19 February 13

Page 16: Performance Testing [not] somebody I used to know

JMeter vs. LoadRunner

Tuesday, 19 February 13

Page 17: Performance Testing [not] somebody I used to know

Cloud Impact?

Force MultiplierTuesday, 19 February 13

Page 18: Performance Testing [not] somebody I used to know

Biggest Drivers for Tools

A r e c o s t s , o p e n a n d extendable languages, integration with popular t e s t f r a m e w o r k s a n d continuous delivery and or deployment, access to high level APIs, cross platform and ease of use.

Tuesday, 19 February 13

Page 19: Performance Testing [not] somebody I used to know

How to select the right tool?

Effective & Efficient Almost as important as the job itself.

Tuesday, 19 February 13

Page 20: Performance Testing [not] somebody I used to know

Think about the price

and cost effectiveness

Tuesday, 19 February 13

Page 21: Performance Testing [not] somebody I used to know

Think about the support

Tuesday, 19 February 13

Page 22: Performance Testing [not] somebody I used to know

Think about the integration

Everything from source c o n t r o l , m o n i t o r i n g , communications, alerting, deployment and beyond.

Tuesday, 19 February 13

Page 23: Performance Testing [not] somebody I used to know

Think about the protocol

HTTP 1999XHR 2008WebSocket 2011

Think about the protocol

Tuesday, 19 February 13

Page 24: Performance Testing [not] somebody I used to know

Environments

environments {start|stop|restart}

We spend a LOT of time waiting for test environments to be provisioned, patched, restarted or deployed.

Tuesday, 19 February 13

Page 25: Performance Testing [not] somebody I used to know

Increased Burn Rate

The rate at which hours (allocated to a project) are being used ...

Tuesday, 19 February 13

Page 26: Performance Testing [not] somebody I used to know

Increased Complexity

Solving for simultaneous equations

Tuesday, 19 February 13

Page 27: Performance Testing [not] somebody I used to know

Analysis Paralysis

“Are we writing scripts to launch a space shuttle?

http://www.flickr.com/photos/gsfc/6385412737/Tuesday, 19 February 13

Page 28: Performance Testing [not] somebody I used to know

Extinct by Instinct

Tuesday, 19 February 13

Page 29: Performance Testing [not] somebody I used to know

Trending Now

“Let’s be *more* agile and promote an iterative cycle that emphasizes working products over product specifications ...

Tuesday, 19 February 13

Page 30: Performance Testing [not] somebody I used to know

In the Future

Tuesday, 19 February 13

Page 31: Performance Testing [not] somebody I used to know

Future is Now

Tuesday, 19 February 13

Page 32: Performance Testing [not] somebody I used to know

Fire Fighting in Production

Tuesday, 19 February 13

Page 33: Performance Testing [not] somebody I used to know

Replicating in Stage

Tuesday, 19 February 13

Page 34: Performance Testing [not] somebody I used to know

A DSL for Test Plans

Tuesday, 19 February 13

Page 35: Performance Testing [not] somebody I used to know

Scaled out in 5 minutes

Tuesday, 19 February 13

Page 36: Performance Testing [not] somebody I used to know

Results Shared in Real Time

Tuesday, 19 February 13

Page 37: Performance Testing [not] somebody I used to know

Short & Sharp Tests

Tuesday, 19 February 13

Page 38: Performance Testing [not] somebody I used to know

In 2013

“ W e h a v e s i g n i f i c a n t l y reduced performance test costs and increased efficiency of performance test efforts.

Tuesday, 19 February 13

Page 39: Performance Testing [not] somebody I used to know

Questions?

Tim KoopmansMelbourne, [email protected]@90kts

contact:locate:email:

blog:follow:

GridinitTuesday, 19 February 13