These values provide the information on the time your project VMs spend in running state during the latest closed billing month. Each value gives the number of VMs with a specific runtime rate (the time the VM was in running state, in % of the overall VM lifetime within the month). The report includes currently existing VMs and the VMs that were removed before the month ended.

Optimization data is the 'Account Optimization Ratio' part of a monthly Summary Report delivered to Project Sponsors, Sales Executives, and Account Managers. Apart from the report, this data is available on the Monitoring page of the Cloud Management Console.
The values given here are true for the moment of closure of the latest billing month.

  • * Normal range: 30% - 70% VM utilization. We assume that the users regularly work with their VMs and stop them when they are not used. The standard working day is eight hours, and in some cases, a VM utilization is prolonged for project needs. If a VM usage fits this scheme, its uptime rate is within the 30-70% range.
  • ** Low utilization: < 30%. The stopped VMs are still billed, and in case a VM is mostly in the stopped state, the bigger part of the VMs price is its down time price. If the VM is in running state for less than 30% of its lifetime, it may be reasonable to remove it and to pass its tasks to another VM. In case there is a need to have separate VMs for some rarely performed tasks, it can be useful to switch from the 'stop/start' utilization pattern to 'run/terminate', when the VM is created to perform a special task and then removed.
  • *** Very high utilization: > 70%. High utilization can be a signal to check whether the instances are really required 24/7, and if they are not, stop them regularly. It is possible to organize automatic scheduled VMs stopping and starting using the Cron rules.