What are Reserved Instances? AWS Reserved Instances are a pricing option wherein customers can “reserve” one or more resources / capacity, for either one or three years. Unlike on-demand where commitment is usually valid per hour, reserved instances are for 1- or 3-year term; and in exchange, the hourly rate per resource is lowered significantly. This works out to 35 - 50% lower EC2 costs compared to similar on-demand instances.
Last month we wrote an article on our Rightsizing component which analyses and recommends a suitable instance type for your application based on standard CloudWatch metrics such as CPUUtlization, NetworkIn and NetworkOut. Today we announce support for capturing memory metrics from CloudWatch, enabling an even better recommendation. While creating a cmpute job, the user gives us consent to capture and push memory metrics to CloudWatch. We do so by installing a CloudWatch agent on each instance provisioned via cmpute.
Cmpute.io is a platform which reduces your AWS EC2 spend across three main areas: Instance Optimization – usage of Spot, Reserved and On-Demand instances Time Optimization – schedule start and stop of instances Performance Optimization – analyse application performance and rightsize instances Time-based Optimization is about the ability to schedule workloads (instances and applications) based on some policies (most relevant for dev/test workloads). Instance Optimization is the automatic usage of Spot Instances at all layers of your application – be it web / app tier or API tier as well as optimal utilization of purchased Reserved Instances across multiple accounts.
What are Spot Instances? Spot instances are deeply discounted instances provided by AWS at 80-90% cheaper rates when compared to on-demand instances. Performance wise, spot instances are comparable to on-demand instances. However, spot instances work on demand-supply economics and if outbid the instance would be taken immediately (with a 2 min termination notice) CMPUTE is a SaaS solution that balances your AWS EC2 workloads over on-demand, spot and reserved instances to achieve up to 85% savings on your EC2 costs.
Spot Instances are great. They are cheap and offer up to 90% savings over On-Demand Instances. By design, they can be taken away at any time. “How would you then run Web / App tier on Spot Instances?” is the million-dollar question that needs an answer. In this post, I will delve into its details. In the end, I am sure you will appreciate the value that Spot Instances provide and also recognize that they can be used for any kind of workload.
We live in the Data Age! Web has been growing rapidly in size as well as scale during the last 10 years and is showing no signs of slowing down. Statistics show that every passing year more data gets generated than all the previous years combined. Moore’s law not only holds true for hardware but for data being generated too. Without wasting time for coining a new phrase for such vast amounts of data, the computing industry decided to just call it, plain and simple, Big Data.
Spot Instances are slowly but surely gaining traction with the enterprise AWS users. Who would want to lose out on a potential savings of up to 90% over On-Demand costs? Not me. Neither should you. In this post, I will explain the basics of Spot Fleet and how it eases the use of native Spot Instances. I will also delve a bit into the missing pieces of Spot Fleet.
Spot Instances have gained popularity and continue to do so at a rapid pace. However, they come with their own set of complexities and challenges. Mitigation plans, if not in place, lead to application downtime and cost you dear. Common strategies include – Never launching all Spot Instances of a single instance type Launching at least 2 instance types are a must for better availability Never launching all Spot Instances in a single Availability Zone