Storage

Owned by Abhi Doddi
Aug 29, 2024
2 min read

  • The purpose of storage recommendations is to show the savings on storage with un-attached storage, orphaned snapshots, size + performance, volume type change.

  • Un-attached Storage

    • When recommending savings for un-attached storage, we look at any data disks that are incurring costs but not attached to any instances. To reduce costs, we recommend them for deletion.

    • The calculation for savings on un-attached storage is the (current MTD spend / current day of the month) * 365.

  • Orphaned Snapshot

    • When recommending savings for orphaned snapshots, we look at any snapshots that have been taken where the source disk was removed. This includes any incremental backups that are taken over a period of time. To reduce costs, we recommend these snapshots for deletion.

    • The calculation for savings on orphaned snapshots is the (current MTD spend / current day of the month) * 365.

  • Size + Performance

    • When recommending savings for size + performance, the goal is to provide an alternative disk to the current one that reduces costs but maintains the performance capability of the workloads needs. There are two factors that are taken into account when making this recommendation. The first is the disk size and the second is the IOPs count.

    • Recommending a new disk simply requires finding a cheaper disk from our price catalog that can manage the current disk’s size and peak IOPs usage and performance.

    • The calculation for savings on switching to a new disk is the ((existing type rate (hourly) - suggested instance rate (hourly))* 24) * 365, and we only show the first two decimal places.

  • Volume Type Change

    • When recommending savings for volume type changes, this is mostly catered to Amazon EBS volume types such as gp. The purpose of this recommendation is to allow users to upgrade into the next generation of their volume type. This also allows them to also upgrade the volume type without stopping the instance.

    • The calculation for VM rightsizing in app services is the ((existing type rate (hourly) - suggested instance rate (hourly)) * 24) * 365, and we only show the first two decimal places.