This is the second part of our series on rightsizing.
In the first part, we covered why rightsizing is an ongoing process that must be followed from time-to-time and what are the different types of Instance families available for right-sizing.
“Knowing is only half the battle won” – what makes rightsizing complicated is :
Which option should I select to get the maximum savings?
How confident I am that the new instance will be able to cover my existing workload?
How certain I am whether the new instance will be compatible with the old instance?
Will, the new instance be able to support my load on NICs, Disks Attached, etc.?
Taking help from an automated tool, that can monitor your cloud infrastructure to generate insightful recommendations might help you save time and money. At Cloudwiry, we have experience in right-sizing 100s of servers for our clients and can help get your workload right.
These are the points taken into consideration while building our Right-sizing calculator:
- VCPUs – target VCPUs >= effective VCPU
- Memory – target memory >= effective memory
- Network Interfaces Attached – target NICs capacity >= NICs attached
- Number of Disks Attached – target Disks capacity >= Disks attached
- Network throughput (Mbps) – target Network throughput >= Network usage
- Reservation Coverage – exclude candidates covered by reservations that cannot be reused/remodelled
- Processor Architecture – Processor architecture for rightsizing candidate must be compatible with the old processor
- HVM vs PV ( AWS Specific)
- Autoscaling group – Exclude instances in an autoscaling group
- Tenancy – Shared/dedicated
(Here is a screenshot from our app where user can see all the relevant information regarding rightsizing an instance along with usage graphs)
Rightsizing Recommendations Filters
Under rightsizing, we include the list of all instances that can meet the workload and are priced less than the current instance.
Sometimes, IT teams need to know the list of options with filters to find the best fit for their usage. Currently, at Cloudwiry we provide the following filters to end-users :
- Current Generation – Recommendations are restricted to the current instance families.
- Latest Generation – Recommendations are restricted to the latest instance families.
- Equivalent memory capacity – For cases where the memory metric is not available for the resource.
- Remain in instance family – Recommendations that are restricted to current instance family (t-series, b-series for example).
- Remain in instance group – Recommendations that are restricted to a group (General Purpose, Compute Optimized, Memory Optimized, etc).
Like all good things, part 2 of our series, Rightsizing is an ongoing process, comes to an end. In part 3, we will deep dive into maximizing your savings by converting part of your instances to burstable workload.