vRealize Operations Manager 6.0.x Sizing Guidelines
search cancel

vRealize Operations Manager 6.0.x Sizing Guidelines


Article ID: 340692


Updated On:


VMware Aria Suite


Use the sizing guidelines for vRealize Operations Manager 6.0.x to determine the configurations to be used during installation.


VMware vRealize Operations Manager 6.0.x


By default, VMware offers Extra Small, Small, Medium, and Large configurations during installation. Size the environment according to the existing infrastructure to be monitored. After the vRealize Operations Manager (formerly known as vCenter Operations Manager) instance outgrows the existing size, expand the cluster to add nodes of the same size.
Characteristics/Node Size Extra Small Small Medium Large Standard Size Remote Controller Large Size Remote Controller
vCPU 2 4 8 16 2 4
Memory (GB) 8 16 32 48 4 16
IOPS See the attached Sizing Guidelines worksheet for details.
Disk Space
Single-Node Maximum Objects 250 2,400 7,000 12,000 1,500 (***) 12,000 (***)
Single-Node Maximum Collected Metrics (*) 70,000 800,000 2,000,000 3,500,000 NA NA
Multi-Node Maximum Objects Per Node (**) NA 2,000 5,000 10,000 NA NA
Multi-Node Maximum Collected Metrics Per Node (**) NA 700,000 1,500,000 2,500,000 NA NA
Maximum Objects for 8-Node Maximum (**) NA NA 40,000 75,000 NA NA
Maximum Metrics for 8-Node Configuration (**) NA NA 12,000,000 20,000,000 NA NA

(*) Metric numbers reflect the total number of metrics that are collected from all adapter instances in vRealize Operations Manager. To get this number, go to the Cluster Management page in vRealize Operations Manager, and view the adapter instances of each node at the bottom of the page. You can get the number of metrics collected by each adapter instance. The sum of these metrics is what is estimated in this sheet.

Note: The number shown in the overall metrics on the Cluster Management page reflects the metrics that are collected from different data sources and the metrics that vRealize Operations Manager creates.

(**) In large, 8-node configurations, note the reduction in maximum metrics to permit some head room.
(***) The object limit for the remote collector is based on the VMware vCenter adapter.
  • Maximum number of remote collectors (RC) certified: 50
  • Maximum number of VMware vCenter adapter instances certified: 50
  • Maximum number of VMware vCenter adapter instances that were tested on a single collector: 30
  • Maximum number of certified concurrent users per node (regardless of node size): 4
  • The maximum number of analytics cluster nodes is 8, regardless of whether they are used for HA. If HA is enabled, the effective maximum is 4 nodes as the other 4 nodes are used for HA. Remote Collectors do not count against the maximum of 8 nodes.
  • An object in this table represents a basic entity in vRealize Operations Manager that is characterized by properties and metrics that are collected from adapter data sources. Example of objects include a virtual machine, a host, a datastore for a VMware vCenter adapter, a storage switch port for a storage devices adapter, an Exchange server, a Microsoft SQL Server, a Hyper-V server, or Hyper-V virtual machine for a Hyperic adapter, and an AWS instance for a AWS adapter.
  • The limitation of a collector per node: The object or metric limit of a collector is the same as the scaling limit of objects per node. The collector process on a node will support adapter instances where the total number of resources is not more than 2,400, 5,000, and 10,000 respectively, on a small, medium, and large multi-node vRealize Operations Manager cluster. For example, a 4-node system of medium nodes will support a total of 20,000 objects. However, if an adapter instance needs to collect 8,000 objects, a collector that runs on a medium node cannot support that as a medium node can handle only 5,000 objects. In this situation, you can add a large remote collector or use a configuration that uses large nodes instead of small nodes.
  • If the number of objects is close to the high-end limit, dependent on the monitored environment, increase the memory on the nodes. Contact Product Support for more details.
The sizing guidelines for vRealize Operations Manager 6.0.x are outlined in the attached spreadsheet.



vRealizeOperationsManagerSizing_6.0.x get_app