Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

vRealize Operations Manager 6.7 Sizing Guidelines (54370)

Last Updated: 2/10/2021Categories: InformationalTotal Views: 22353Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Details

This article provides information on using the sizing guidelines for vRealize Operations Manager 6.7, to determine the configurations used during installation.

Solution

By default, VMware offers Extra Small, Small, Medium, Large, and Extra Large configurations during installation. You can size the environment according to the existing infrastructure to be monitored. After the vRealize Operations Manager instance outgrows the existing size, you must expand the cluster to add nodes of the same size.

vRealize Operations Node

Remote Collector (RC)

Extra Small

Small

Medium

Large

Extra Large

Standard

Large

Configuration

vCPU

2

4

8

16

24

2

4

Default Memory (GB)

8

16

32

48

128

4

16

Maximum Memory Configuration (GB)

N/A

32

64

96

N/A

8

32

vCPU: Physical core ratio for data nodes (*)

1 vCPU to 1 physical core at scale maximums

Network latency for data nodes (*****)

< 5 ms

Network latency for remote collectors (*****)

< 200 ms

Network latency for agents (to vRealize Operations node or RC) (*****)

< 20 ms

Datastore latency

Consistently lower than 10 ms with possible occasional peaks up to 15 ms

IOPS

See the attached Sizing Guidelines worksheet for details.

Disk Space

Objects and Metrics

Single-Node Maximum Objects

350

3,500

11,000

20,000

45,000

6,000 (****)

32,000 (****)

Single-Node Maximum Collected Metrics (**)

70,000

800,000

2,500,000

4,000,000

10,000,000

1,200,000

6,500,000

Maximum number of nodes in a cluster

1

2

8

16

6

60

60

Multi-Node Maximum Objects Per Node (***)

N/A

3,000

8,500

16,500

40,000

N/A

N/A

Multi-Node Maximum Collected Metrics Per Node (***)

N/A

700,000

2,000,000

3,000,000

7,500,000

Maximum Objects for the configuration with the maximum supported number of nodes (***)

350

6,000

68,000

200,000

240,000

Maximum Metrics for the configuration with the maximum supported number of nodes(***)

70,000

1,400,000

16,000,000

37,500,000

45,000,000

End Point Operations agent

Maximum number of agents per node

100

300

1,200

2,500

2,500

250

2,000

(*) It is critical to allocate enough CPU resources for environments running at scale maximums to avoid performance degradation. Refer to the vRealize Operations Manager Cluster Node Best Practices in the vRealize Operations Manager 6.7 Help for more guidelines regarding CPU allocation.

(**) Metric numbers reflect the total number of metrics that are collected from all adapter instances in vRealize Operations Manager. To get this number, you can go to the Administration page, expand History and generate an Audit report.

(***) In large configurations that consist of more than 8 nodes, note the reduction in maximum metrics and objects to permit some head room. This adjustment is accounted for in the calculations.

(****) The object limit for the remote collector is based on the VMware vCenter adapter.

(*****) The latency limits are provided in Round Trip Time (RTT)

What's new in vRealize Operations Manager 6.7 sizing

Manage larger environments with the same footprint: Up to 30% more objects than in 6.6.x.

Manage more vCenter Servers: Up to 120 vCenter Servers (it was 60 in 6.6.x).

Collect from larger vCenter Servers: Up to 65000 objects; achieved by a large Remote Collector (8 vCPU and 32GB of RAM)

Support for scale down CPU configuration: Reclaim up to 4 vCPUs from the Large and Extra Large node VMs if the cluster is not running at the upper limits, and the CPU usage in node VMs is less than 60%.  The cluster will perform better if the nodes stay within a single socket (don't cross NUMA boundaries).

Important Notes

The sizing guides are version specific, please use the sizing guide based on the vRealize Operations version you are planning to deploy.

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.

Other Maximums

Maximum number of remote collectors

60

Maximum number of vCenter adapter instances

120

Maximum number of vCenter on a single collector

100

Maximum number of concurrent users per node (*)

10

This is when the cluster is running with all nodes filled with objects or metrics at maximum levels on a 4 large node cluster.

Maximum number of certified concurrent users (**)

300

Maximum number of the End Point Operations agents

10,000

* The maximum number of concurrent users is 10 per node with objects or metrics at maximum levels (For example, 16 nodes Large with 200K objects can support 160 concurrent users).
** The maximum number of concurrent users is achieved on a system configured with the objects and metrics at 50% of supported maximums (For example, 4 nodes Large with 32K object).

VDI use case

A large node can collect more than 20,000 vRealize Operations for Horizon objects when a dedicated remote collector is used.

A large node can collect more than 20,000 vRealize Operations for Published Apps objects when a dedicated remote collector is used.

Constraints

Extra small and small node are designed for test environment and POC, we do not recommend to scale-out small node more than two nodes and we do not recommend to scale out extra small node.

If you have >1 node, then alll nodes must be scaled equally. No mixing of nodes with different sizes.

Snapshot impact performance. Snapshot on the disk causes slow IO performance and high CPU co-stop values which degrades the performance of vRealize Operations.

In HA, each object is replicated in some nodes of a cluster, hence the limit for HA based instance is two times less compare to non HA.

vRealize Operations HA supports only one node failure. Avoid single-point-of-failure by putting each nodes into different host in the vSphere cluster.

Scaling Tips

Scale up, not out.

Use the configuration which has the least number of nodes.
Example: For 180000 objects, deploy as 4 Extra Large nodes instead of 12 Large nodes. You will save half the CPU.

You can increase RAM size instead of increasing both RAM and CPU

This is useful if the number of objects is close to the upper limit. Check that there is enough RAM on the underlying hardware

Example: Large node has 48GB and the number of objects are closed to 20000. You can increase up to 96 GB. This assumes the underlying ESXi has >96 GB per socket.

Collectors

The collection process on a node will support adapter instances where the total number of objects is not more than 3,000, 8,500, 16,500 and 40,000 on small, medium, large and extra large multi-node vRealize Operations Manager clusters respectively.
For example, a 4-node system of medium nodes will support a total of 34,000 objects.
However, if an adapter instance needs to collect 12,000 objects, a collector that runs on a medium node cannot support that as a medium node can only handle 8,500 objects. In this situation, you can add a large remote collector and pin the adapter instance to the remote collector or scale up by using a configuration that supports more objects.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

vRealizeOperationsManagerSizing_6.7

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Dell EMC PowerEdge with NVDIMM 永続メモリ (Peristent Memory) のサポート (54444)

KB
•
ESXi 5.5 以降に対する Fujitsu ServerView Suite CIM プロバイダ (55064)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vRealize Operations Manager

VMware vRealize Operations

Related Versions:

VMware vRealize Operations Manager 6.7.x

Take Our Survey

Support Assistant