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.

Performance Testing And Beyond


Published on

A presentation tries to move the discussion on performance testing from a simple, "will it support x users" to a focus on application optimisation.

  • D0WNL0AD FULL ▶ ▶ ▶ ▶ ◀ ◀ ◀ ◀
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

Performance Testing And Beyond

  1. 1. Performance Testing and Beyond<br />Peter Brown<br />CEO<br />Ecetera<br />
  2. 2. Performance is the number 1 feature<br />1. Speed<br />2. Instant Utility<br />3. Software is Media<br />4. Less is More<br />5. Make it Programmable<br />6. Make it Personal<br />7. RESTful<br />8. Discoverabilty<br />9. Clean<br />10. Playful<br />
  3. 3. Imperceptible differences have an effect 1<br />Data driven results<br />Strong linear correlation<br />Users become less engaged<br />
  4. 4. Imperceptible differences have an effect 2<br />Number of searches per day decreases in proportion to the delay<br />Effect persists even after the delay is removed<br />
  5. 5. Perceptible differences have an effect too!<br />
  6. 6. Common view of Performance Testing<br />
  7. 7. Why do performance testing?<br />So you know, ahead of time, across varying user loads, the system’s<br />Responsiveness<br />Throughput<br />Reliability<br />After all changes that could effect performance and before real users get access to the system<br />So you can<br />Know if it will meet operational objectives, and ...<br />Gauge the effect of architectural decisions<br />Optimize the environment for optimal performance<br />Identify code hotspots<br />Etc ...<br />
  8. 8. The effect of architectural decisions<br />Does the application behave the way it was architected?<br />In the context of the transaction are any anti-patterns evident?<br />
  9. 9. Environment optimisation<br />Business processes<br />JVM/App Server<br />Garbage Collection<br />Threading<br />Clustering<br />Caching<br />Database<br />Web proxy<br />VM tuning<br />Database<br />Frontend engineering<br />Load balancing<br />Protocol offload<br />TOE<br />SSLisation<br />Storage<br />Misc black boxes<br />
  10. 10. Identify code hotspots<br />Where is the transaction spending most time<br />Which component is using the most CPU time<br />Which components are memory hogs<br />
  11. 11. Application/Testing Lifecycle<br /><ul><li>The last thing between a great idea and launch is SVT
  12. 12. #1 Performance anti-pattern
  13. 13. Performance should be addressed across the lifecycle</li></li></ul><li>Performance COE<br />
  14. 14. Cloud based testing<br />Load injection in the Cloud<br />SilkPerformerCloudBurst<br />Gomez Reality Load<br />LoadRunner in the Cloud<br />Keynote LoadPro<br />Amazon + software <br />Load Test Environment<br />Amazon<br />Rackspace<br />
  15. 15. Summary<br />Performance Matters – A lot<br />Even imperceptible performance improvements can make a big difference<br />Performance testing can add a lot of value across the application lifecycle<br /> The cloud makes it easy to create and remove test environments and load injectors<br />