360 likes | 496 Views
Why Assumptions about Cloud Performance Can Be Dangerous to Your Business. Ron Wilson, Director Cloud Strategy. Ron.Wilson@compuware.com. Agenda. Why Does Performance Matter? Brief Overview of Web and Cloud Performance Challenges Real-World Data: How Are Cloud Providers Performing?
E N D
Why Assumptions about Cloud Performance Can Be Dangerous to Your Business Ron Wilson, Director Cloud Strategy Ron.Wilson@compuware.com
Agenda • Why Does Performance Matter? • Brief Overview of Web and Cloud Performance Challenges • Real-World Data: How Are Cloud Providers Performing? • Cloud Optimization Opportunities • Key Takeaways • Q&A
Why Performance Matters: Revenue 2 4.3 % second slowdown reduction in revenue/user* found that a 400 0.59 % stated that a millisecond delay fewer searches/users* Noticed that users who experience the fastest page load times 50 % view more pages/visits than users experiencing the slowest page load times* reduced page load times from ~7 seconds to ~2 seconds, 50 leading to a increase in revenue and 7–12 % % reduction in hardware costs* Source: Steve Souders @ Velocity Conference 2009
Why Web Performance Matters: Customer Satisfaction 40% of Consumers will abandon a site if made to wait Consumer expectations for how quickly a web page should load How long consumers will wait for a page to load before abandoning 5% 1% 12% 2% 30% 10% 36% 27% 17% 60% • Lost revenues • Increased costs • Reduced customer satisfaction • LOB dissatisfaction with IT “eCommerce Web Site Performance Today” white paper August 2009
Typical Web Application Delivery The Web Application Delivery Chain 3rd Party/Cloud Services Browsers and devices Local ISP Users Load Balancers Web Servers Mobile Components App Servers Internet MajorISP DB Servers Mobile Carrier Storage Mainframe Network Content DeliveryNetworks Traditional zone of control
The Challenge of Ensuring Quality Web Experiences Systems management tools: “OK” …user is NOT happy The Web Application Delivery Chain • Inconsistent geo performance • Bad performance under load • Blocking content delivery • Incorrect geo-targeted content • Network peering problems • Bandwidth throttling • Inconsistent connectivity • Poorly performing JavaScript • Browser/device incompatibility • Page size too big • Too many objects • Low cache hit rate • Configuration errors • Application design issues • Code defects • Insufficient infrastructure • Network peering problems • Outages • Network resource shortage • Faulty content transcoding • SMS routing / latency issues • Configuration issues • Oversubscribed POP • Poor routing optimization • Low cache hit rate Traditional zone of control Traditional zone of control Zone of customer expectation Zone of customer expectation Zone of customer expectation Zone of customer expectation
The Business Impact of Poor Web Experiences Systems management tools: “OK” …user is NOT happy The Web Application Delivery Chain Ineffective SLA’s and partner relationships • Lost revenue • Brand damage • Dissatisfied customers • Increased call center volume • Increased costs Ineffective SLA’s and partner relationships Over investment in infrastructure Over spending on CDNs Traditional zone of control Zone of customer expectation
Moving Web Applications to the Cloud: Benefits • Elastic and scalable • Focus on my business while someone manages infrastructure The Web Application Delivery Chain 3rd Party/Cloud Services Browsers and devices Local ISP Users Load Balancers Web Servers Mobile Components App Servers Cloud Internet MajorISP DB Servers Mobile Carrier Storage Mainframe Network Content DeliveryNetworks Traditional zone of control
The Problem: The Cloud Creates Performance Concerns The Web Application Delivery Chain • Cloud is opaque • Loss of visibility and control • Traditional tools don’t apply 3rd Party/Cloud Services Browsers and devices Local ISP Users Users Load Balancers Web Servers Mobile Components App Servers Cloud Internet MajorISP DB Servers Mobile Carrier Storage Mainframe Network Content DeliveryNetworks Traditional zone of control
The Answer: Adopt an “Outside-In” User Point of View • Full understanding of performance from user perspective The Web Application Delivery Chain 3rd Party/Cloud Services Browsers and devices • Test/monitor your site the way your customers use it: • What they do (key pages and transactions) • Where they do it (geographic locations) • How they do it (browsers and mobile devices) • When they do it (normal and peak usage) • Determine the impact on their behavior and your business Local ISP Users Users Load Balancers Web Servers Mobile Components “Outside-in” customer point of view App Servers Internet MajorISP DB Servers Gomez Platform Mobile Carrier Storage Web Cross-Browser Testing Web Load and Performance Testing Web Performance Management Web Performance Business Analysis Mainframe Network Content DeliveryNetworks Traditional zone of control
The Problem: The Cloud Creates Performance Concerns The Web Application Delivery Chain My users • Cloud is shared • Others can affect my performance 3rd Party/Cloud Services Browsers and devices Local ISP Load Balancers Web Servers Other users My app Mobile Components App Servers Other app Other app Other app Internet Other users MajorISP DB Servers Mobile Carrier Storage Mainframe Other users Network Content DeliveryNetworks
The Answer: Collective Intelligence • Multiple contributors help diagnose issues for everyone The Web Application Delivery Chain My users Cloud is shared 3rd Party/Cloud Services Browsers and devices Local ISP Load Balancers Web Servers Other users My app Mobile Components “Outside-in” customer point of view App Servers Other app Other app Other app Internet Other users MajorISP DB Servers Mobile Carrier Storage Mainframe Other users Network Content DeliveryNetworks
Cloud Apps: You Must Be Able to Pinpoint Problems The Web Application Delivery Chain My users 3rd Party/Cloud Services Browsers and devices Local ISP Load Balancers Web Servers Other users Mobile Components App Servers Internet Other users MajorISP DB Servers Mobile Carrier Storage Mainframe Other users Network Content DeliveryNetworks
A Year In The Cloud An End-user Perspective on Cloud Performance
What We Measured • Cloned reference Web application deployed across various IaaS and PaaS providers • Added various services such as a Content Delivery Network, when available • Structured application to highlight Cloud Performance issues
How We Measured • Various locations around the world • Backbone and Last Mile locations • Every 15 minutes, 24/7, for over 1 year • Used a strict definition of availability
Not All Clouds Perform the Same Way Average Response Time of Reference Application, as measured from US backbone locations
Taking the Long View – Response Time © 2010 Gomez – All Rights Reserved
Amazon EC2 Europe West (Dublin) Performance • Response time for sample transaction of reference application hosted on Amazon EC2 Europe West (Dublin), as measured from major European cities
Enough Scary News… … let’s see something good for a change
Unique Opportunities for Optimization • Better performance, for little work, at no extra cost?
Best Practice: Define Your Goals and Build a Plan Align goals across your organization Why are we moving to the cloud? Common goals include: Additional Capacity – How much capacity do we need during normal and peak times? Improved End-User Experience – What performance goals are we trying to deliver against? Greater Elasticity – How quickly can the provider we select ramp up to meet our needs? Flexible Bursting – How fast do we need to be able to access additional capacity? If only there was a button to push!
Best Practice: Keep Your End-users in Mind Test your cloud applications the same way your customers use it: • What they do? • Customers care about completing tasks NOT whether the homepage is available • Where they do it from? • Your customers don’t live in the cloud, test from their perspective across multiple devices and browsers • When they do it? • Test at peak and normal traffic levels, to find all the problems • What expectations do customers have? • Is 4 seconds fast enough or does it have to be quicker? Geographic disparities 4 sec’s 22 sec’s
Best Practice: Performance Testing Cloud Capabilities Evaluate vendors based on your goals… Capacity • Test vendors to 15-20% past estimated capacity goals Elasticity • Baseline end-user performance before & after testing • Test during pre-deployment and in production • Ramp elasticity testing to peak levels Burstability • Isolate the cloud elements from other infrastructure to test • Test the “failover process”
Best Practice: Set SLAs to Match Your Goals Set SLAs based on your goals… • End-user availability and response times • Capacity & elasticity objectives • Burstability goals Set SLAs based on how you are using the cloud…
THANK YOU Questions? Ron.Wilson@compuware.com