Early lifecycle performance testing & optimization without the grief
•
4 likes•1,274 views
If you would like a copy of the slides, please email jessica.murphy@compuware.com 75% of users will go to a competitor's site if performance is poor. And what's concerning is that slow performance is most likely when your site is under peak load – exactly when you want your site to be operating at it's best. You probably know that Web Load Testing should be a standard part of the application delivery lifecycle. If you haven't made Web Load Testing a part of your process it can feel like going through the stages of grief to do so. Let us help you through the denial and anger to acceptance and even excitement, when you see how the right solution can save time and help you deliver a better application. Learn: • How to include Web Load Testing as part of your application delivery lifecycle • How to work through the “5 stages of grief” from denying there is a problem to, getting the team all on the same page and accepting there is a better way • Why an integrated solution with deep diagnostic tools is the answer
Recommended
Recommended
More Related Content
More from Compuware APM
More from Compuware APM (20)
Recently uploaded
Recently uploaded (20)
Early lifecycle performance testing & optimization without the grief
- 2. Why Web Load Testing?
- 5. Application Performance Matters: Poor Performance Impacts Business Results
- 6. Web Load Testing is How You Avoid This heavy traffic volume “It’s an unforgivable mistake that cost them thousands of dollars,” she said. “After all the money spent with the hype of the collection, no one thought it would translate to web traffic?” Media Analyst
- 7. Don’t use your customers as load test dummies
- 8. Integrating Performance Testing Without the Grief
- 9. Agile Development Practices • Most of us made the transition to Agile …
- 10. To push out changes faster Story Points Developme Testing Estimate nt Sprint Timeline Remaining Production Team Velocity
- 11. And you think you are in control Story Points Developme Testing Estimate nt Sprint Timeline Remaining Production Team Velocity
- 12. But maybe you are not? Story Points Developme Testing Estimate nt Sprint Timeline Remaining Production Team Velocity
- 13. Missed Goals and Estimates Story Points Missed Developme Testing Estimate nt Production Missed Remaining Goal Team Velocity
- 14. When to Test With What Tools?
- 15. Why you may feel like you are in the 5 stages of Grief when you talk to the team about web load testing
- 16. Denial • Risk is low, I’m not as big as the other guys • My application developers are really good • My IT department would tell me if there was an issue • We are using “proven” third party technology • We’re going to beta test it
- 17. Performance Land Mines- everyone has a stake • Too many Database • Traffic estimates incorrect Statements • Poorly provisioned hardware • Synchronized to Death • No consideration of end user • Too chatty on remoting devices or latency channels • Misconfigured CDN • Wrong use of O/R Mappers • Load Balancing Issues • Memory Leaks • Networking/infrastructure • Bloated Web Frontends issues • Problematic 3rd parties
- 18. Performance Regression Identified in early Load Testing Version Control History Lookup
- 19. Anger • There may be some head butting and resistance
- 20. Web Load Testing is Hard • I can’t get the information I need from Marketing • We don’t know how to test realistic user load as we don’t know the use cases nor the expected load in production • We don’t have the tools, expertise or hardware resources to run large scale load tests • We don’t have the time to do this and deliver • It is too much effort to create and especially maintain testing scripts • Commercial tools are expensive and sit too long on the shelf between test cycles • We don’t get actionable results for our developers
- 21. Convince the team real users matter
- 22. Depression • Whoa this is way too much to tackle at this point
- 23. Out of Time? Expensive? Short Staffed? • Easy Tools • Open Source Tools or • “Pay as you Go” Services • Integrate into Dev Cycle
- 24. Can’t act on results • Don’t get the right data • Don’t understand data • Can’t duplicate errors
- 25. Acceptance • Do we agree it’s important • Do we think we can get the resources we need? • Can we make this work?
- 26. Integrate all the stakeholders into the performance lifecycle • Line of Business Managers • Product Managers • Marketers • Interface Designers • Application Developers • Architects • Quality Assurance Teams • Infrastructure/Operations Teams • Help Desk Staff Quality is a Collective Function. Everybody owns a piece of the puzzle. Avoid at all costs: Individual Success, Collective Failure
- 27. Transitioning from grief to success Performance Management Performance Threshold Traditional Time Development Testing Production Continuous Performance Performance Threshold Management Time Development Testing Production Developing Load Testing Problem R olution es Production
- 28. How Compuware Can Help
- 29. Gomez Approach - 360º Web Load Testing • Load Testing identifies performance symptoms – but where‘s the issue? • PurePath technology follows all transactions through the Application
- 30. Advantage of 360º Web Load Testing • Hours/days to solve problems • Weeks/months to 360o Load Testing • Session is solve problem recorded, eliminatin • gMultiple reproduce need to test cycles errors •• Drill down to Poor communication offending line of between QA and code developers • Eliminates testing iterations
- 31. Gomez Approach -360º Web Load Testing The Only Unified View of Web Application Performance Under Load Full End to End Visibility Measure Load impact on User Experience From the First Mile… …to the Last Mile Cloud Customer Browsers s Private Public Local Data Center 3rd Party/ ISP Virtual/Physical Environment Cloud Services DB App Web Load Mainframe Servers Servers Servers Balancers Major ISP Storage Content Network Delivery Networks Web Mobile WAN Services Components Optimization Mobile Carrier Employees Devices Employees Visibility Volume Value Measure the impact of the load The power of a global cloud test Unique value of the Last Mile to on the systems under test with a network to drive the load needed accurately stress 3rd parties and view from DynaTrace and enable from the locations needed to measure performance from the agile DevOps collaboration stress any web application end user perspective Performance matters… no Correlate performance to On-Demand Volume at the click matter where in the world your system utilization of a button users are located
- 32. More Information • White paper • Instant load test • Free Ajax edition dynaTrace • 360 demo link • Blog: To Load Test or Not to Load Test: That is not the question • E-Book Web Load Testing for Dummies Contact: laura.strassman@compuware.com Websites: www.compuware.com/gomez www.dynatrace.com
- 33. Questions?
- 34. © 2011 Compuware Corporation — All Rights Reserved
Editor's Notes
- If some of you’re wondering what is web load testing, simply put, it’s not having to say sorry when your web site or application is unavailable to your customers. There have been a number of high profile incidents in the past few months. The one referenced here put the organization in the news for the wrong reasons and resulted in loss of revenue. <<BUILD>> But this is not a one-off and can effect even high-tech that you may think would be more immune: just the other night I couldn’t reserve my place in a queue to buy the cool new smartphone on the market. This is my second time in 2 weeks trying to do this and goes to show that volume is not always a one-time issue…you really need to work with marketing or the business to understand the end customer trends. Web load testing is how you determine how much traffic your website or web application can accommodate without “breaking” or causing your customers to blog about how painfully slow it is.Web load testing is how you ensure that your customers have a great experience on your site regardless of the number of visitors at any given time.
- We need to show this diagram later – with the testing cycles in it.
- Briefly we want to advise around some types of performance testing where they fit in… then we web load test before going to market.
- Common Mistake:$ cost of marketing campaigns associated with driving peak traffic – driving priorityBusiness Objectives and KPIsvs the IT team’s ability to deliver.Impact on Business:Lost sales due to the site not being availableLessons Learned (case example):Nationwide – $1.5 Mill marketing to MicrositeBOA – Used microsite to generate leads – drove traffic to find breaking point (What can they support?)Informing Business of what the site can handle before they drive traffic to it
- WithdynaTrace in yourLoadTesting Environment yougetfullvisiblityintowhathappenswithinthe App whenloadissimulated. dynaTracefollowseveryexecutedtransactionthroughyoursystemandshowsexactlywherethingsgowrong
- Read slide build
- In order to ensure great customer experience when launching web and mobile applications, we need to take a user-focused approach to design, collaboration and testing. The evolution of today’s web applications require that Web Load Testing takes a holistic view of the entire Web Application Delivery chain and ensure end customer performance from the first-mile to the last mile, providing:1. Visibility from within the firewall to empower our teams, improve collaboration and accelerate problem resolution and application delivery2. Volume of the cloud to generate realistic load against todays application infrastructure without the costly hardware and setup times that can be involved in build your own internal network3. Value through end user focused load testing that provides the only accurate way to understand how load impacts end user experience and ultimately your business. Gomez 360 solution is the first and only solution on the market to address these 3 key requirements and <<<BUILD>>>