Sizing Guidelines for ControlUp v8.x

This guideline article provides information to properly size the required ControlUp components used during installation and upgrades.

The article is relevant for the ControlUp Hybrid Cloud solution for version 8.x only. Sizing guidelines for v7.x can be found via this link

ControlUp offers scalability for both small and large organizations. We recommend working in the N+1 configuration for the Monitor cluster and for the data collectors for high availability.

Note on ControlUp Monitor scalability - the scalability limit of a single Monitor node is 400,000 concurrent processes. The actual limit of VDI machines per Monitor node depends on the avg. number of concurrent processes per VDI machine.
For a customer with an avg. of 160 concurrent processes per machine, a single Monitor node will support 2,500 VDI machines.

Note: For your convenience, we've created an interactive online sizing calculator where you can input the exact details of your environment and get the recommended number of v8 Monitor nodes. You can access the calculator via this link

VDI based workloads

The sizing numbers below are based on environments where end-users are running on VDI machines (e.g. Windows 7 or Windows 10 VMs with or without 3rd party software such as Citrix Virtual Apps and Desktops, VMware Horizon or Microsoft WVD).
The main factor to consider is the number of VDI machines being managed by ControlUp. Please note that when managing more than 500 VDI machines, 
disabling the process flat views in the real-time console is a mandatory requirement. 

ControlUp Monitor and Real-time Console hardware sizing 

ControlUp Component ControlUp Monitor Node(*) ControlUp Real-Time Console(***)
VDI Workloads  0 - 1,000 1,000 - 2,000 2,000 - 4,000(****) 0 - 1,000 1,000 - 2,000 2,000 - 4,000
vCPU(**) 4 8 8 2 2 2
RAM 16 16 32 4 6 8

(*) For environments with more than 2,500 VDI machines, additional Monitor nodes should be deployed, see below configuration examples for 5,000, 20,000 and 50,000 VDI machines.
(**) 2.8Ghz clock speed or higher. 
(***) Per console instance, based on a fully optimized console, see this article
(****) The scalability limit of a single Monitor node is 400,000 concurrent processes, so the actual limit of VDI machines per Monitor node depends on the avg. number of concurrent processes per VDI machine.

For a customer with an avg. of 160 concurrent processes per machine, a single Monitor node will support 2,500 VDI machines.

VDI Sizing Examples

Example Configuration For 500 VDI machines
ControlUp Component # of VM's / Instances  vCPU (per instance) RAM (per instance) Notes
Monitor Nodes(*) 2  16  N+1 configuration
RT Console N/A 2  Per console instance 
Data Collector See the Data Collector section at the end of the article.

The example above is based on an avg. of 160 concurrent processes per VDI machine and on an N+1 configuration.

Example Configuration For 5,000 VDI machines
ControlUp Component # of VM's / Instances  vCPU (per instance) RAM (per instance) Notes
Monitor Nodes(*)  3  32  N+1 configuration
RT Console N/A 2  Per console instance 
Data Collector See the Data Collector section at the end of the article.

The example above is based on an avg. of 160 concurrent processes per VDI machine and on an N+1 configuration.

Example Configuration For 20,000 VDI machines    
ControlUp Component # of Instances  vCPU (per instance) RAM (per instance) Notes
Monitor Nodes(*) 9  8  32  N+1 configuration
RT Console N/A  2 Per console instance 
Data Collector See the Data Collector section at the end of the article.

The example above is based on an avg. of 160 concurrent processes per VDI machine and on an N+1 configuration.

Example Configuration For 50,000 VDI machines    
ControlUp Component # of Instances  vCPU (per instance) RAM (per instance) Notes
Monitor Nodes(*) 21 8  32  N+1 configuration
RT Console N/A 2 8  Per console instance 
Data Collector See the Data Collector section at the end of the article.

The example above is based on an avg. of 160 concurrent processes per VDI machine and on an N+1 configuration.

- - - - -

RDSH based workloads
The sizing numbers below are based on environments where the end-users are running on RDSH based servers. The main factor is the number of concurrent sessions being managed using ControlUp. Note that when managing more than 2,000 concurrent user sessions, disabling the process flat views in the real-time console is a mandatory requirement. 

ControlUp Component ControlUp Monitor Node ControlUp Real-Time Console(**)
RDS Sessions  0 - 5,000 5,000 - 10,000(***) 0 - 5,000 5,000 -  10,000
vCPU(*) 4 8 2 2
RAM 16 32 4 8

(*) 2.8Ghz clock speed or higher.
(**) Per console instance, based on a fully optimized console, see this article. 
(***) Based on approx. 20 processes per RDS session.

For further information regarding the Data Collectors - Click here.

RDSH Sizing Examples

The scalability limit of a single Monitor node is 400,000 concurrent processes, so the actual limit of RDS hosts per Monitor node depends on the avg. number of concurrent processes per host incl. the host. On average, a single Monitor node will support 10,000 concurrent sessions.
**The numbers below will vary between organizations due to the number of sessions running on each host. 

Example Configuration For 5,000 RDS Sessions running on 250 RDSH hosts
ControlUp Component # of Instances  vCPU (per instance) RAM (per instance) Notes
Monitor Nodes(*) 2 4 16  N+1 configuration
RT Console N/A 2  Per console instance 
Data Collector See the Data Collector section at the end of the article.

The example above is based on an avg. of 200 concurrent processes per an RDSH host and 20 processes per session on an N+1 configuration.

Example Configuration For 20,000 RDS Sessions running on 1,000 RDSH hosts
ControlUp Component # of Instances  vCPU (per instance) RAM (per instance) Notes
Monitor Nodes(*) 3  8  32  N+1 configuration
RT Console N/A  2 Per console instance 
Data Collector See the Data Collector section at the end of the article.

The example above is based on an avg. of 200 concurrent processes per an RDSH host and 20 processes per session on an N+1 configuration.

Example Configuration For 50,000 RDS Sessions running on 2,500 RDSH hosts
ControlUp Component # of Instances  vCPU (per instance) RAM (per instance) Notes
Monitor Nodes(*) 5 8 32  N+1 configuration
RT Console N/A 2 8  Per console instance 
Data Collector See the Data Collector section at the end of the article.

The example above is based on an avg. of 200 concurrent processes per an RDSH host and 20 processes per session on an N+1 configuration.

Data Collectors

Configuring dedicated data collectors for Hypervisors, EUC connections and NetScalers is always recommended, in large environments the data collector should run on a dedicated VM.

You can get more information about the component here and see why a data collector is important both for the environment and the performance of the real-time console you interact with. -> ControlUp Data Collector.

There's a matter of which data source you're assigning to the data collector. For example, adding vCenter can cause more RAM to be utilized based on the number of machine records that we'll get via the vSphere API. Adding Citrix sites uses more CPU due to the queries that are being performed by the PowerShell API. NetScaler can use more network due to the amount of data that we're getting via the Nitro API.

The numbers in the sizing chart below are representing the number of records that the API is passing.

  • When linking a data source which is a VMware\Hyper-V\XenServer\Nutanix hypervisor, we query hosts, machines, datastores & virtual disks. 
  • EUC environments like Citrix Virtual Apps and Desktops \ VMware Horizon, we query topology (delivery groups/desktop pools), brokers\connection servers, machines & sessions. 
  • NetScaler we'll query Appliance info & metrics, Load Balancers, HDX Sessions & Gateways.  
ControlUp Data Collector
  0 - 2,000 (**) 2,000 - 5,000 (**) 5,000 + (**)
vCPU 2 4 4
RAM 8 8 8

(**) The numbers are representing the number of records that the API is passing per ControlUp's API query.

 

Got a question regarding the sizing? let us know at support@controlup.com

Powered by Zendesk