CPN211 My Datacenter Has Walls That Move - AWS re: Invent 2012

797 views

Published on

How do you think about computing resources in a world where you can launch and terminate computational capacity in minutes? Amazon EC2 provides a powerful platform to access vast computational resources at the click of a button or a simple API call. It is also very different from operating your own data center or having to managed fix assets in a co-location facility. This talk walks you through examples of how the cloud enables more efficient capacity planning, provides guidance in how developers and organizations can manage thousands of instances efficiently, and highlights tools that make it easy for you to plan your capacity needs, even when those needs might require you to provision the equivalent of a small data center at short notice.

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
797
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

CPN211 My Datacenter Has Walls That Move - AWS re: Invent 2012

  1. 1. My Datacenter Has Walls That Move Deepak Singh Principal Product Manager - Amazon EC2#reinvent
  2. 2. http://www.wired.com/wiredenterprise/2011/12/nonexistent-supercomputer/
  3. 3. Image: Windsordi
  4. 4. Image: wdr3
  5. 5. NewCo
  6. 6. Small biotech
  7. 7. New business unit Small biotech
  8. 8. Image: EMSL
  9. 9. Algorithms
  10. 10. AlgorithmsBioinformatics
  11. 11. Algorithms BioinformaticsScientific Analysis
  12. 12. More servers?
  13. 13. Space?
  14. 14. Power?
  15. 15. Risk
  16. 16. Capital
  17. 17. Big project
  18. 18. Good problem to have?
  19. 19. Image: Joriel Jimenez
  20. 20. Constraints
  21. 21. CPU Memory DiskNetworking Power Cooling
  22. 22. Credit: Pieter Musterd
  23. 23. Remove constraintsCredit: Pieter Musterd
  24. 24. Embrace change
  25. 25. Not constrained by ...
  26. 26. Space
  27. 27. Power & Cooling
  28. 28. Capital
  29. 29. Agents of change
  30. 30. 1. On Demand computing
  31. 31. For when you needFor whom you need
  32. 32. 2. Elasticity
  33. 33. Rinse, Repeat
  34. 34. 3. Flexibility
  35. 35. Choose the right instance type
  36. 36. For when you needFor whom you needFor what you need
  37. 37. Most Apps Low Cost M1 Standard M3 Standard Most Apps Fast High CPU Scale-out Compute Memory-intensive High Memory AppsCompute + Network Througput Micro Inexpensive Cluster Compute Memory-intensive Cluster Computing Cluster High Memory Lots of low-latency Cluster GPU Parallel GPGPU Computing IOPS High I/O Petabyte Scale Lots of Throughput High Storage
  38. 38. Choose the right price
  39. 39. For when you need For whom you need For what you needFor how much you need
  40. 40. Reserved Instances
  41. 41. Light UtilizationMedium Utilization Heavy Utilization
  42. 42. Spot Instances
  43. 43. 100% On-demand Reserved capacity
  44. 44. What is the value of my data?
  45. 45. How much am I willing to pay for a compute cycle?
  46. 46. Ask yourself theright questions
  47. 47. NewCo
  48. 48. What is the baseline for each team?Image: Mad African
  49. 49. What is the length of a typical project?Image: Peter Morville
  50. 50. Are we using the right instance type(s)?
  51. 51. Can we leverage Spot Instances?
  52. 52. Adapt over time
  53. 53. Remove constraintsCredit: Pieter Musterd
  54. 54. Making it real
  55. 55. Source: Adrian Cockroft (Netflix)
  56. 56. Multiple applications
  57. 57. Different utilization
  58. 58. Source: Adrian Cockroft (Netflix)
  59. 59. Spiky
  60. 60. Long term forecast?
  61. 61. Not easy
  62. 62. Find the rightinstance type(s)
  63. 63. c1?m3?cc2?
  64. 64. Cover your baseline
  65. 65. Light Utilization RI
  66. 66. On Demand +Spot Instances
  67. 67. Source: Adrian Cockroft (Netflix)
  68. 68. Daily usage
  69. 69. Occasional spikes
  70. 70. Elastic MapReduce +Reserved Instances + Spot Instances
  71. 71. Source: Adrian Cockroft (Netflix)
  72. 72. Growth over time
  73. 73. Planning horizon
  74. 74. Months
  75. 75. Weeks
  76. 76. Days
  77. 77. Less risk
  78. 78. Accurate forecasts
  79. 79. BetterAccurate forecasts
  80. 80. Global infrastructure
  81. 81. 9 regions25 availability zones38 edge locations
  82. 82. International expansion
  83. 83. Disaster recovery
  84. 84. Geographic replication
  85. 85. Hot spare
  86. 86. In Conclusion
  87. 87. Think beyond the data center
  88. 88. What you need
  89. 89. When you need
  90. 90. Where you need
  91. 91. We are sincerely eager to hear your feedback on thispresentation and on re:Invent. Please fill out an evaluation form when you have a chance.

×