Released: October 2017
This release presents new functionality that allows the user to right-size VMs using individual measures such as ‘peak’ or ‘average’. It also presents a new report focusing on VM storage utilisation.
Different workloads must be optimised and right-sized based on different measures depending on the behaviour profile of that workload. The approach so far in Capacity Planner has been to use the 95th %ile for CPU right-sizing and the 99th %ile for memory right-sizing. Allocating enough resources to accommodate that demand while leaving a 20% growth buffer for unexpected peaks. For some VMs, this is not sufficient. There are machines that lie dormant for long periods of time and have very short high CPU spikes. As a result, it may be more appropriate to base the right-sizing of this on CPU peak rather than 95th %ile.
Also, it may be possible that multiple memory metrics are being used to model various aspects of memory demand. This feature allows the user to choose which memory metric to use to right-size. For example, providing the flexibility to right-size based on consumed memory rather than active memory.
The interface for right-sizing has been updated as follows.
When you right-size, the user will be given the option of which CPU or Memory metric to use (if applicable) and then which measure to use:
Selecting a measure gives the user the ability to choose between the 5th, 25th, 50th (median), 75th, 95th, 99th, max or min measures.
As a reminder, the percentile figure is the measure defining the amount of time a metric was at a particular value over the course of the baseline used in the scenario. For example, if the user picks the 99th %ile, for CPU rightsizing, that means that the value used for CPU will be that value which the metric has spent 1% of its time at or above over the baseline.
The UI workflow in a migration has now been updated to consider this extra flexibility. The user is no longer asked prior to the migration if a right-size is to take place. Rather, the user is asked after the migration if machines that have been moved are to be right-sized.
The operations list has also been updated to provide detail on the measure used during right-sizing.
A VM storage summary report has been added to the default list of standard reports. This report is aimed at identifying potential wastage in environment particularly when thick provisioning is used. It will compare the total allocated VMDK storage or virtual disk storage for a VM with the total drive utilisation and determine the difference in allocation vs demand. It will order, by default, on free VMDK space, from largest to smallest.
The input parameters are as follows:
The grouping filters allow this report to be filtered. Further grouping filters may be added as product releases update. VM State allows the user to select those which are ‘current’ and those which are ‘removed’. Current VMs are those VMs which are still actively generating data. For investigative or exploratory work, it is recommended that this ‘current’ state is used for reporting.
The user can also expand on drive details for more information on the VM drives and utilisation compared to allocated thick storage.
Click the links below to view other versions of Capacity Planner release notes.
|Capacity Planner Release Notes 102||Released: October 2019|
|Capacity Planner Release Notes 101||Released: August 2019|
|Capacity Planner Release Notes 100||Released: May 2019|
|Capacity Planner Release Notes 99.2||Released: March 2019|
|Capacity Planner Release Notes 99||Released: December 2018|
|Capacity Planner Release Notes 95||Released: May 2018|
|Capacity Planner Release Notes 94||Released: March 2018|
|Capacity Planner Release Notes 93||Released: January 2018|
|Capacity Planner Release Notes 92||Released: December 2017|
|Capacity Planner Release Notes 91||Released: October 2017|
|Capacity Planner Release Notes 90||Released: September 2017|