When you create the cluster nodes that make up vRealize Operations Manager, additional best practices improve performance and reliability in vRealize Operations Manager.

Deploy vRealize Operations Manager analytics cluster nodes in the same vSphere cluster.

If you deploy analytics cluster nodes in a highly consolidated vSphere cluster, you might need resource reservations for optimal performance.

Determine whether the virtual to physical CPU ratio is affecting performance by reviewing CPU ready time and co-stop.

Deploy analytics cluster nodes on the same type of storage tier.

To continue to meet analytics cluster node size and performance requirements, apply storage DRS anti-affinity rules to ensure that nodes are on separate data stores.

To prevent unintentional migration of nodes, set storage DRS to manual.

To ensure balanced performance from analytics cluster nodes, use ESX hosts with the same processor frequencies. Mixed frequencies and physical core counts might affect analytics cluster performance.

To avoid a performance decrease, vRealize Operations Manager analytics cluster nodes need guaranteed resources when running at scale. The vRealize Operations Manager Knowledge Base includes sizing spreadsheets that calculate resources based on the number of objects and metrics that you expect to monitor, use of HA, and so on. When sizing, it is better to over-allocate than under-allocate resources.

See Knowledge Base article 2093783.

Because nodes might change roles, avoid machine names such as Master, Data, Replica, and so on. Examples of changed roles might include making a data node into a replica for HA, or having a replica take over the master node role.