Understanding the Instance Optimization Details Report

Understanding the Instance Optimization Details Report

#380390

The Instance Optimization Details report displays instance-specific details for the instance type group selected from an optimization opportunity or Optimization Overview report.

Open the Instance Optimization Details report, by clicking on a hyperlinked value in the Count column from a supported optimization opportunity tabular report.

The Instance Optimization Details report for ASGs is covered in Working with Auto Scaling Groups.

Note: Cloud instances that do not have adequate information for recommendation analysis are not included in the Instance Optimization Details report. For example, this would include guests with no or incomplete benchmark data.

To learn more watch the video:

The following features are available for the data on this dashboard:

  • To return to the parent Public Cloud Optimization page, use the Back button in the top-right corner of the page. Do not use the browser's Back button for navigation within Densify as this exits Densify.
  • For each supported Instance Optimization Details report, you can use the Export to Excel button to export the tabular data for external analysis. See Exporting Report Data for details on using the Export to Excel feature.

The Instance Optimization Details dashboard consists of:

  • A tabular report—The columns of the tabular report change depending on the selected instance type. Refer to the Table: Instance Optimization Details Tabular Report Columns below for details.
  • A lower pane with system details—Based on the selected system in the tabular top pane, various details and settings for the system are available in separate tabs, such as system resource utilization charts, system details, optimization approvals and modifying system attributes. See Reviewing the Instance Details for details on each tab.

Reviewing the Instance Optimization Details Table

Table: Instance Optimization Details Tabular Report Columns

Component/Column Name

Description

Included For

Account | Project | Subscription

The instance's parent environment. This corresponds to the:

  • AWS Linked Account, or
  • GCP Project, or
  • Azure Subscription.

There may be additional cloud connections required to collect the account data. Refer to the corresponding cloud connection section for details.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Environment

The instance's parent account. This corresponds to the:

  • AWS Payer Account, or
  • GCP Project ID, or
  • Azure Account.
  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Cluster

The cluster corresponds to a geographic region.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

System

The system name is a hyperlink that takes you to the Impact Analysis and Recommendations page. You can review instance-specific details. See Viewing the Public Cloud Impact Analysis and Recommendation Report.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

System ID

A unique key assigned by the public cloud vendors to identify this instance.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Overall Status

Identifies the overall status of the optimization results based on Optimization Type and potential $ Savings/Month :

Optimal

These groups of cloud services are currently optimal. Optimization type is just right and there are no savings for this group.

Identified Risk

These groups of cloud services are at risk. This status typically occurs when the savings amount is less than $0 (i.e. when you need to spend money to mitigate risk).

Identified Risk status is also present when the savings amount is $0, but optimization type is upscale, upsize, or upsize to optimal family. This situation occurs when services are inactive, but they will need to be upscaled or upsized when they resume activity to mitigate risk.

Savings Opportunity

These groups of cloud services have saving opportunities, which occurs when their savings amount is greater than $0.

Savings opportunity status is also present when the savings amount is $0, but optimization type is terminate, modernize, modernize to optimal family, downscale, downsize, or downsize to optimal family. This situation occurs when services are inactive, but have a recommendation of terminate, modernize, downsize or downscale when they resume activity to save money.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Optimization Type

The recommended action for this instance. See Optimization Type Descriptions and Color-Coding for a description of each recommendation.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Recommendation Reason

The reason for the Optimization Type recommendation.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Current Instance Type

Based on the data collected, the current instance type is listed.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Current RI Coverage (%)

This is the percentage of reserve instance (RI) coverage available for the current instance. Flexible RIs are taken into consideration when calculating the percentage of RI coverage. However, convertible RIs are included in the calculation depending on the RI coverage assessment Densify settings.

For individual compute or database instances, the coverage percentage is either 100% or 0%. Coverage between 0 and 100% occurs when Flexible RIs are converted into partial coverage.

Contact your Cloud Advisor or support@Densify.com to review your RI candidate policies and RI coverage assessment Densify settings.

  • EC2, RDS

Recommended Instance Type

Based on optimization analysis, the recommended catalog instance type is listed.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Defer Recommendation Until Current RI Coverage Expires

Defer recommending an instance type change until reserved instance coverage for this instance expires. Values include:

  • Yes—defer instance type recommendation due to RI coverage;
  • No—do not defer instance type recommendation; this is also the case for "Terminate" recommendation;
  • "-" —not applicable; this is also the case for "Just Right" recommendation.

A n icon on this column indicates that instances that are RI-constrained should not be modified to the recommended instance type at this time since the current instance has existing reserved instance coverage. When the applicable reserved instances expire (as indicated by the "Current RI Expiry Date"), then the instance can be modified to the recommended instance type.

This field is based on AWS Defer Recommendation settings. Contact your Cloud Advisor or support@Densify.com to review your AWS Defer Recommendation settings.

  • EC2, RDS

Current RI Expiry Date

If Defer Recommendation Until Current RI Coverage Expires = "Yes", then the expiry date of the reserved instance, which is currently providing coverage for this instance, is displayed.

Note: The RI expiry date is not displayed for an instance with Optimization Type = " Just Right" or "Terminate" .

  • EC2, RDS

Predicted Uptime (%)

When using pay-per-use pricing models, we need to know the amount of time each instance has been running to accurately estimate future costs.

The predicted uptime (%) for an instance or container, is based on the percentage of hours CPU utilization data is present in the historical interval, as specified in the policy settings.

Predicted uptime %, for new instances or containers, that started mid-way through the historical interval, is calculated from the time/date that the instance was started as opposed to the beginning of the interval, resulting in more accurate prediction for the future.

Click on the Predicted Uptime Details tab to review the uptime details for the selected instance.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Current Estimated Cost ($)

The current estimated per instance cost is determined by multiplying the on-demand price of the current instance type by uptime.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Recommended Estimated Cost ($)

Recommended estimated cost is calculated based on multiplying the on-demand price of the recommended instance type by the uptime.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

$ Savings/Month

The estimated current and recommended instance cost is used to calculate savings per month (i.e. current estimated cost - recommended estimated cost).

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Effort

[High|Medium|Low|None]

This column describes the effort required to investigate and implement the Densify recommendations. Effort for each instance is calculated by rule-driven analytics based on factors (such as instance family change, storage change, data quality checks, feature changes, etc.) that can be configured in the policy settings and rule set which captures best practices.

Click on the Effort Details tab to view the factors that contribute to the effort level. See Reviewing the Workload Charts and Additional Details Tabs, below.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Implementation Method

[Manual|Self-Optimizing|-]

Specifies whether the instance with the recommended Optimization Type is configured for Self-Optimizing or Manual actioning.

The implementation method value is derived from the Self-Optimizing Automation Setup policy or from an instance Self-Optimizing Automation override, which takes precedence over the policy.

To make an instance Self-Optimizing Automation override, see Editing System Attributes . The updated implementation method value is displayed in this column after Densify analysis and the reporting database tables have been updated (i.e. after an RDB populate).

See Approving Cloud Recommendations for more information on the implementation method in the Self-Optimizing Automation workflow.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

 

Current vCPUs

The current value for CPU allocation.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Recommended vCPUs

The recommended value for CPU allocation.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Current CPU Benchmark

The current CPU benchmark.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Recommended CPU Benchmark

The recommended CPU benchmark.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Current Memory Allocation (GB)

The current value for memory allocation.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Recommended Memory Allocation (GB)

The recommended value for memory allocation.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

%CPU Usage (High)

The percentage of highest CPU workload.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

%CPU Usage (Low)

The percentage of lowest CPU workload.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Active Memory Usage (%)

The percentage of active memory utilization.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Memory Usage (%)

The percentage of memory utilization.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

OS

The operating system running on the instance.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Ideal CPU Allocation

The minimum CPU allocation required to not violate the policy high limits on the recommended instance.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Ideal Memory Allocation

The minimum memory allocation required to not violate the policy high limits on the recommended instance.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

CPU Allocation Efficiency (%)

The allocation CPU efficiency (i.e. ideal allocation / recommended allocation) is measured in percent and shows the amount of CPU resources truly require by the workload.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Memory Allocation Efficiency (%)

The allocation memory efficiency (i.e. ideal allocation / recommended allocation) is measured in percent and shows the amount of memory resources truly require by the workload.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Sort By

By default, the tabular report is sorted by Overall Status and Optimization Type columns. In the top-right corner of the tabular report, a dropdown selection of sorting options are available. For details on sorting behavior, see Viewing Cloud Optimization Reports.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Summary Total

In the top-right of the tabular report, the total number of Instances and Savings/Month for implementing the recommendations are displayed. The total number of instances displayed is a total of all the instances in this optimization instance type group (this number corresponds to the number in the Count column of the parent optimization opportunity tabular report). The amount of savings per month is a sum of all the savings/month for each instance listed and can be negative if the recommendation is upsize or upsize to an optimal family.

  • EC2, RDS, Spot Instances
  • Virtual Machines
  • Compute Engine
  • Optimization Overview

Note: The following details are not included in this report: Disk Allocations (Current | Recommended), Individual Disk Partitions at Risk, Disk Usage and Parent.

Optimization Type Descriptions and Color-Coding

The following descriptions and color coding apply to all AWS, Azure and GCP tabs.

Note: Not all optimization types are supported for all cloud providers.

Table: Optimization Type Color-Coding Summary

Optimization Type

Description

Just Right

This instance is optimally sized for the workload.

In general the following upsize recommendations incur additional costs. The cost increase is determined by comparing on-demand pricing for the current and recommended instance. The increased cost is required to alleviate application risk. Iff you have an RI or SP for the recommended upsize instance, there could be cost savings. This would still be an upsize recommendation.

Upsize - Optimal Family

This instance should be upsized to a more optimal instance family. This will improve the workload's performance and reduce risk.

If the workload can be moved to larger instance in a different family and still reduce cost, this then becomes a Modernize recommendation. e.g. t2.medium-Linux to m3.medium-Linux

Upsize

This instance should be upsized to an instance within the same instance family. The hosted workload needs an instance with more CPU and\or memory resources.

e.g. r3.large to r4.xlarge, both are in the "Memory Optimized r" instance family.

Upscale

This recommendation applies to ASGs only and indicates the ASG needs increase compute capacity by adjusting the maximum group size.

It may be more cost effective to use a larger instance for this ASG.

Downsize recommendations reduce the allocated resources as your workload has likely been over-provisioned. Once the recommendation has been determined from CPU and memory utilization, it is further verified against policy-defined limits, before the downsize or terminate recommendations are made.

Terminate

This instance should be terminated, as it is idle. An instance is determined to be idle if it has very low CPU utilization, network and disk I/O over an extended period of time. This will save you money.

Downsize - Optimal Family

This instance should be downsized to an instance belonging to an instance family that more closely suits your workload's utilization.

When you downsize, CPU and\or memory will be decreased to better suit your workloads. Utilization will improve with no impact on performance. This will save you money. e.g. d2.medium-Linux to m4.medium-Linux

Downsize

This instance should be downsized to an instance within the same instance family.

As indicated above, CPU and\or memory will be decreased to better suit your workloads. Utilization will improve with no impact on performance. This will save you money. e.g. m3.large-Linux to m3.small-Linux

Downscale

This Auto Scaling group should be downscaled to decrease the compute capacity by adjusting the minimum group size.

The following modernize recommendations move your workload to a more modern instance type without changing the resource allocation, cost or performance, at a minimum. Your costs could decrease and/or you may benefit from potential utilization and performance improvements.

Modernize - Optimal Family

This instance should be modernized to an instance belonging to a more optimal instance family. The cost of the new instance type will be less than the existing cost.

Allocated resources are not being removed and moving to an instance with more current hardware, you may also benefit potential utilization and performance improvements.

When you modernize, you will not decrease performance but will decrease cost.

Modernize

This instance should be modernized to an instance within the same instance family. The cost of the new instance type will be less than the existing cost and as indicated above you may also get utilization and performance improvements.

For example, moving to a new generation of the same instance family (e.g. m3.large to m4.large).

Reviewing the Instance Details

Clicking on any row in the tabular report shows more detailed system information for that instance, in the tabs on the lower pane:

  • Resource Utilization Metrics: Cloud | Transformation Tab—The charts on this tab show the utilization for various workloads for the selected the instance.
  • Note: If no metrics are available, then the corresponding chart is not displayed.

    These workload charts show hourly min/max and sustained activity for the selected system. Use the left/right arrows to scroll though the various workload charts.

    Workload charts display current Sustained Activity in blue, while Sustained Activity on the recommended instance type is shown in green. The minimum and maximum utilization values are shown as vertical lines above and below the coloured block. The median is indicated as a black line within the coloured block. The average is indicated in, in brackets, in the sub-title of the chart.

    The scale used on the Y-axis is scaled dynamically to match the range of data. Where applicable, the pink line indicating the policy high limit, is shown, and the setting of the Y-axis scale also accounts for the policy limit setting. This is applicable to both public cloud and virtual optimization charts for Resource Utilization Metrics.

  • System Information Tab—Click on this tab to see allocated resources and some of the organizational attributes that have been set for this guest.
  • Effort Details Tab—This tab lists the factors that contribute to the effort required to investigate and implement the Densify recommendations. Effort for each instance is calculated by rule-driven analytics based on factors (such as instance family change, storage change, data quality checks, feature changes, etc.) that can be configured in the policy settings and through analysis rule sets. A description of each rule and its impact on the effort to move the current instance to the recommended instance type are provided.
  • Contact your Cloud Advisor for further details on the policy settings and rule set configured for your environment.

  • Predicted Uptime Details Tab—This tab shows a pie chart with the uptime details for the selected instance.
  • Approvals Tab—This tab allows you to approve or disallow the recommended action of the selected instance. The approval setting of the instance allows for manual implementation or full automation with integrated infrastructure applications, such as Terraform. See Approving Cloud Recommendations for an overview of this feature.
  • Edit System Attributes Tab—This tab provides you with the ability to edit system attributes for the selected system. See Editing System Attributes for details.

Quartiles in the Resource Utilization Charts

To learn more watch the video,

In charts, workload data for each system is shown in four different bars (two yellow and two red), called quartiles, to show minimum, average, sustained and peak values. When used in the analysis, quartiles provide a good representation of system activity because the weighted scoring for sustained and peak activity produces a more accurate assessment of workload utilization patterns and requirements.

Quartiles are calculated in the following manner:

  • Workload activity is collected every five minutes, which totals 12 times per hour.
  • The 12 values are then re-ordered in descending order and separated into equal sample sizes (quartiles), with each quartile having three values. Each quartile represents 25% of operational time.
  • The bottom of the first quartile shows the minimum value, the next quartile shows average values, the top of the third quartile shows the sustained value and the top of the fourth quartile shows the peak value.

Editing System Attributes

The Edit System Attributes tab in the lower pane of the Instance Optimization Details report allows you to edit specific attributes of the system selected from the top pane.

This feature is supported via the Densify API for all editions.

The following default system attribute categories are available for editing:

  • Business
  • Routing
  • Self-Optimizing Automation Overrides

Contact your Cloud Advisor if you require additional system attributes to be exposed for editing.

Attribute changes are displayed accordingly in the Edit Systems Attributes tab.

Densify optimization and reporting database updates are required before the saved values are reflected in the Instance Optimization Details tabular report and footer. For example, if you update and save one of the Self-Optimizing Automation Overrides attributes, you can see the updated value in the Edit Systems Attributes tab and extract the updated attribute value from the Densify API. However, the Instance Optimization Details tabular report and footer will not display the recommendation results of the updated value until analysis has been performed and the reporting tables have been updated via the overnight scheduled job.