Summary Tab

The Summary tab displays summary of resource utilization information. Gauges graphically present the total processor and memory utilization. The display differs slightly between the tab for all compute pools and the tab for a specific compute pool and between reserved compute pools and instance-based compute pools.

For reserved compute pools, the gauges present the portion of resources consumed by your virtual machines compared to the total resources purchased. For instance-based compute pools, the gauges present the portion of resources consumed by your virtual machines compared to the total resources allocated. The utilization graphs changes over time as your consumption, purchases, and allocations of resources change. Resources consumed are the 95^th percentile of consumption.

Around the gauges are resources consumed, allocated, and purchased.

• Consumed resources – in use in all active virtual machines.
• Allocated resources – sum of resources defined within all created virtual machines.
• Purchased resources – purchased by the organization.

Beneath the gauges are several ratios:

• Virtual processing units – in use in active virtual machines versus total, in all created virtual machines.
• Virtual Machines – active virtual machines versus all created virtual machines.
• Storage – storage used by all created virtual machines versus purchased storage.

Note: On instance-based compute pools, no storage is purchased; therefore, only the storage used by all created virtual machines is shown.

The final element in the summary utilization is the burst mode button, one each for processor and memory. For more information on Burst mode, see Resource Bursting.

Resource Utilization in All Compute Pools Tab

Reserved Compute Pools

For Reserved compute pools:

1. Click All Compute Pools.
2. Click Reserved compute pool.
3. Click All VMs or Active VMs to calculate allocated resources.

The utilization information presented includes:

• One set of gauges, processor and memory, per compute pool.
• Allocated and purchased resources.
• Buttons to enable or disable burst mode.
• Environment processor, memory, virtual processing units, and virtual machine usage: Active versus Total.
• Environment storage: Used versus Purchased.

Instance-Based Compute Pools

For Instance-Based compute pools:

1. Click All Compute Pools.
2. Click Instance based compute pool.
3. Click All VMs or Active VMs to calculate allocated resources.

The utilization information presented includes:

• One set of gauges, processor and memory, per compute pool.
• Allocated resources.
• No buttons for burst mode; burst mode is not available for instance-based compute pools.
• Environment processor, memory, virtual processing units, and virtual machine usage: Active versus Total.
• Environment storage: Used only.

Resource Utilization in a Specific Compute Pool Tab

Reserved Compute Pools

For resource utilization in a specific compute pool tab:

1. Select a specific reserved compute pool.
2. Click Summary.
3. Click All VMs or Active VMs to calculate allocated resources.

The utilization information presented includes:

• One set of gauges, processor and memory, for the selected compute pool.
• Allocated resources.
• Consumed and purchased resources.
• Buttons to enable or disable burst mode.
• Compute pool processor, memory, virtual processing units, and virtual machine usage: Active versus Total.
• Compute pool storage: Used versus Purchased.

Instance-Based Compute Pools

For a specific Instance-Based compute pool:

1. Select a specific instance-based compute pool.
2. Click Summary.
3. Click All VMs or Active VMs to calculate allocated resources.

The utilization information presented includes:

• One set of gauges, processor and memory, for the selected compute pool.
• Allocated resources.
• Consumed resources only.
• No buttons for burst mode; burst mode is not applicable to instance-based compute pools.
• Compute pool processor, memory, virtual processing units, and virtual machine usage: Active versus Total.
• Compute pool storage: Used only.

Purchased versus Allocated versus Consumed

One of the key differentiators of The Enterprise Cloud versus other cloud providers is over-subscription: you can deploy more virtual machines than you purchased resources for. As you allocate more resources, consume more resources, or purchase more resources the gauges will present an accurate state of your environment.

When a virtual machine is running idle or not using 100% of its allocated processor and memory resources those resources are made available to other running virtual machines or can be deployed to new virtual machines. To achieve the maximum value for your Enterprise Cloud environments, it is ideal to run them near 85% usage at all times.

See the Difference between purchased, allocated, consumed, and burst resources for a description of the various categories of resources.

Gauge Features

Gauges permit a quick view of the processor and memory resource utilization in a compute pool. The gauges are slightly different between reserved compute pools and instance-based compute pools.

Reserved Compute Pool

Gauge features of a reserved compute pool:

• The colored shell around the gauge shows allocated resources as a percentage of purchased resources.
• The bar shows consumed resources as a percentage of purchased resources.
• Bursting permits consumed resources over 100% of purchased.

Instance-Based Compute Pool

Gauge features of an instance-based compute pool:

• The colored shell around the gauge shows allocated resources as a percentage of allocated resources; always 100%.
• The bar shows consumed resources as a percentage of allocated resources.
• Bursting is not permitted, consumed resources are never over 100% of allocated.

Gauge States

The color of the bar on a gauge is a visual indicator of resource utilization. The bar must be in one of four states, each with a distinctive color:

State	Color	Utilization	Performance
Normal	Gray	processor within 0-69% memory within 0-64%	Performance normal
Warning	Yellow	processor within 70-84% memory within 70-84%	Performance normal, but warrants careful monitoring
Error	Red	processor greater than 85% memory greater than 90%	Performance degraded Reserved compute pools: consider purchasing more resources or enabling bursting Instance-based compute pools: consider adding virtual machines to the Internet service
Burst	Green	processor greater than 0% memory greater than 0%	Performance normal, but charges incurred when exceeding 100% Note: Bursting not applicable in instance-based compute pools