ControlUp Sizing Guidelines

This guideline should help organizations properly size Console/Monitor/Data Collector per Concurrent sessions.

 

RDSH based workloads

 

The sizing numbers below are based on networks where the majority of end users run on RDSH based servers (with or without 3rd party software such as Citrix XenApp or Horizon View). The main factor is the number of concurrent sessions being managed using ControlUp. Please 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. In addition, configuring dedicated data collectors for Hypervisors and XenDesktop sites is always recommended, in large environments the data collector should run on a dedicated VM.

Note: Dedicated Data Collectors MUST be configured to ease up resources, each Hypervisor/XD Site should be configured with a dedicated data collector on a dedicated VM (not shared with the Monitor/Console/IOP).

 

VDI based workloads

 

The sizing numbers below are based on networks where the majority of end users run on VDI based endpoints (e.g. Windows 7 or Windows 10 VMs with or without 3rd party software such as Citrix XenDesktop or Horizon View). The main factor is the number of VDI endpoints being managed using ControlUp. Please note that when managing more than 500 VDI endpoints  disabling the process flat views in the real-time console is a mandatory requirement. In addition, configuring dedicated data collectors for Hypervisors and XenDesktop sites is always recommended, in large environments the data collector should run on a dedicated VM.

Note: Dedicated Data Collectors MUST be configured to ease up resources, each Hypervisor/XD Site should be configured with a dedicated data collector on a dedicated VM (not shared with the Monitor/Console/IOP).

  • Please use the bottom scroll, to view all columns

RDSH Workloads

Concurrent Sessions

Monitor

Realtime Console

Data Collector

0-1000

2 x 2+ GHz CPU

4 GB RAM

2 x 2+ GHz CPU

4 GB RAM

Monitor can be used

1000-2000

2 x 2+ GHz CPU

8 GB RAM

2 x 2+ GHz CPU

8 GB RAM

Monitor can be used

2000-5000

4 x 2+ GHz CPU

16 GB RAM

2 x 2+ GHz CPU

8 GB RAM

2 x 2+ GHz CPU

4 GB RAM

5000-20000

8 x 2+ GHz CPU

32 GB RAM

2 x 2+ GHz CPU

12 GB RAM

2 x 2+ GHz CPU

8 GB RAM

VDI Workloads

0-500

4 x 2+ GHz CPU

8 GB RAM

2 x 2+ GHz CPU

6 GB RAM

Monitor can be used

500-2000

8 x 2+ GHz CPU

16 GB RAM

2 x 2+ GHz CPU

8 GB RAM

2 x 2+ GHz CPU

4 GB RAM

2000-5000

8 x 2+ GHz CPU

32 GB RAM

2 x 2+ GHz CPU

8 GB RAM

4 x 2+ GHz CPU

16 GB RAM

On-Premises Server

All Env'

2 x 2 GHz CPU

8 GB RAM

Insights On-Premises Server

Minimum Server Requirements

12 x 2+ GHz

16 GB RAM

Physical server recommended, RAID 0 or 1+0, OS Windows 2008 R2/2012 R2, 2016 

SQL Server (for On-Premises installations)

Server

 

 

Disk

10 GB

 

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request
Powered by Zendesk