Sunderland Digital - Cloud Performance – Pitfalls, Hints and Tips

Looking at the history of designing for app performance and what impact the cloud is having.

Transcript

1. Cloud Performance – Pitfalls, Hints and Tips David Owen - @vMackem - https://uk.linkedin.com/in/davidowen9
2. About me • 13+ Years IT industry • App Support, Integration Engineering, VMware Engineer/Architect/Strategist, Converged Infra specialist, Private and Public IaaS specialist. • Sectors – Defence, Finance, Channel Partners & Vendors. • Speaking at corp events, meetups, conferences etc etc. • Local VMware user group leader
3. Dev? EH? What?
4. ITs struggle against 2ND LAW OF THERMODYNAMICS
5. The second law of thermodynamics states that the total entropy can only increase over time for an isolated system. The total entropy can remain constant in ideal cases where the system is in a steady state (equilibrium) or undergoing a reversible process. The increase in entropy accounts for the irreversibility of natural processes, and the asymmetry between future and past.
7. Who Had The Power 90s & 00s – Pre Cloud = Server Huggers - Ops
8. Who has the power now - Cloud Era = Uber Nerds – Developers
9. Who REALY has the power = The Money – The Business
10. TRADITIONAL VRS CLOUD NATIVE
11. Stack Architecture vSphere Design Welcome to my world
12. Build your own Cloud!
13. How to get around lazy code in traditional Arch? Blame the Infra Guy! Tune the system
14. Compute • Symmetric Multi-Processing • vCPU to core ratios • Types of OS Storage: • Block Size • TB vrs TiB • IOPS • Read/Write Ratios Storage: • RAID • Block Size • TB vrs TiB Memory: • NUMA • Page sharing • Swapping VM: • Disk Alignments • Number of CPUs • Hardware assisted Network: • What speed should vNics be • IP Storage • vMotion • TCP Offload • Latency Traditional Performance Considerations & bottlenecks
16. Now things are much more granular
17. Cloud native – The game has changed New World Concepts and taking advantage of old: • Agile Software Dev Philosophy • Polyglot • DevOps • Microservices • Continuous Delivery • Distributed data fabrics • Stateless BUT GUESS WHO IS RESPONSIBLE NOW
18. What has cloud unleashed Agility, elasticity, availability, and cost efficiencies – but software needs to be engineered for cloud platforms in order to realise that.
20. Open issues: • New engineering methodologies • New architectural practices • Maintaining quality throughout when releasing control • New tools needed to engineer for the cloud • Choice of overlapping cloud services Cloud isn't easy though! Well, Easier for start-ups! ECO system of Clouds Services
21. Eco System - The Buffet Cart
23. Things to Consider • Still need to ‘tune’ the VMs • Constant Performance • Encryption • Geo Regions • Benchmark!! • Load/Scale Testing • Find your baseline • ALWAYS MEASURE PERFORMANCE • Right size your VM • Azure • AWS • Know your limits • AWS IaaS Tips Some useful resources 10 Tips to improve perf on AWS SC2 Tips for perf on AWS Azure Storage Perf Tips • Storage • Architect your VMs with the correct Disk Config • Azure • AWS • Networking – Think outside the box (CDN) • AWS
24. Thank You