Performance and Success: Key Elements to Consider in the Cloud
Download as PPTX, PDFā¢0 likesā¢360 views
The document discusses the importance of preparing for and managing cloud performance, highlighting the challenges of application scaling and reliability. It provides tips for handling peak loads, such as utilizing caching, implementing scaling systems, and conducting performance load tests to identify bottlenecks. The document emphasizes the value of setting performance targets and the need for ongoing monitoring to optimize cloud application performance.
Performance and Success: Key Elements to Consider in the Cloud
- 1. Excellence in Cloud Performance Performance and Success Key Elements to Consider in the Cloud Craig Wesely Irwin [email protected]
- 2. The Cloud - Fact or Fiction? ļ The Cloud = āIt Just Worksā ļ All applications behave and scale the same way ļ Theoretical analysis works when capacity planning for the cloud ļ Texas Style - Bigger is better ļ If my web or mobile app crashes, then thatās a good thing. 2
- 3. Todayās Situation ļ Web & Mobile Apps Continue to Crash ļ Slow Response Times ļ Why? 3
- 4. So youāre now in the cloud, how will you prepare for the unexpected?... 4
- 5. So youāre now in the cloud, so how do you respond to the expected? 5
- 6. The Peak Load Challenge Load Server & Cloud ļµ Rapid Load Ramp-Up ļµ Fixed Capacity ļµ Scalability ļµ Snowball Effect ļµ Application Transparency 6
- 7. Tips & Suggestions ļµ #1 For peak and high load ļµ Have backup āminimalistic start/landing pagesā ļµ Small is Fast ļµ #2 Extensive use of Front End Cache systems ļµ Optimize the cache solution, consider Varnish ļµ Less traffic is less problem, no direct DB access ļµ #3 Implement Scaling & Queuing System ļµ Redirect excess traffic using Load Balancer ļµ Create Informative āWaitā pages ļµ Bottom Line: Like a good boy scout ļµ Always be prepared : Test the solution before launch 7
- 8. Why Run A Performance Load Test ? Is the site stable? When does it crash? How can I make it faster? Can my application scale? 8
- 9. Capacity vs. Load 9
- 10. Test Environment vs. Production Environment 10
- 11. Load Test 1 to 1 ļ Load Maximum Throughput Point of collapse ā How many users can we handle? ā What is a good result? Complete failure Nr of users ļ Behavior in the āDanger Zoneā ā Does the application become Response time ā unstable above load maximum? ļ Problem Analysis ā Where are the bottlenecks? Nr of ā How to fix them? users 11
- 12. Do you have Performance Targets? Examples ļµ Stable beyond 100,000 Concurrent users ļµ Able handle 100,000 page views per hour ļµ < 4 second average response time ļµ Top 5 in our industry ļµ Our peak time response time shall be better then competitionās ļµ 95% of our users shall make a travel selection for purchase in less then 30 seconds 12
- 13. LoadTest Findings ļµ #1 Identify the Backend Calls ļµ Database calls donāt kill your application ļµ Lack of caching does! ļµ #2 Check the delivery of static Content ļµ Optimize the cache solution, consider Varnish ļµ Consider using a CDN, if needed ļµ #3 Web Infrastructure ļµ Load Balancer ļµ Server model ļµ Bandwidth ļµ Scaling & Failover 13
- 14. Know Your Numbers - Not all Web & Mobile Apps are equal 14
- 15. Numbers Donāt Lie ā Eliminate Subjectivity ļ Establish a baseline ļ My start page | Login | Book a flight ļ Response Time ā Average 3.2 sec ļ Typical Values ā Median 2.5 sec ļ Standard Deviation 2.8 sec ļ SLA 99.9% ļ 95% is better than 11.8 sec 15
- 16. WebPerformance Monitoring for the Cloud 1 UP/Down 2 Browser 3 Application 4 Correlation ļ Basic Monitor ļ Browser ļ Analytics ļ Inside ļ Alerting ļ Scenarios ļ Trend monitoring ļ Vital Signs ļ Up ā down ļ Analytics ļ Complex ļ Basic SLA ļ Response time Application ļ Drill Down ļ SLA on ļ Root cause applications ļ Consolidation with other system 16
- 17. End User Performance Monitoring ā Whatās the value? 17
- 18. Tips & Suggestions ļµ #1 Set Goals ļµ Uptime ļµ Performance ļµ #2 Hate the average ļµ Work with the exceptions ļµ Remove the 10 Worst transactions every month ļµ #3 Fire drill ļµ Help identifying problems ļµ Correlation of data 18
- 19. Cliff Notes ā¢ Performance Testing will help you discover the weakest link in advanceā¦ ā¢ Saving you time and $$$ ā¢ Check your numbers...Know your application ā¢ They donāt lie ā¢ Plan for the unexpected... ā¢ It happens everyday All systems have a weak spot ā what is 19 yours ?
- 20. Excellence in Cloud Performance Thank You!
- 21. Contact Apica ļ Web ā www.apicasystems.com ļ Twitter ā @apicasystems ļ Email ā [email protected] ā [email protected] ļ Phone ā 1-800-701-5721 21
Editor's Notes
- #17: Logos