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.

 

0 - 1,000 Concurrent Sessions

 

Component Name

#of CPU Cores

RAM (GB)

Notes

Real-time Console

1

2

Per console instance

Monitor Service

2

4

 

Data Collector

N/A

N/A

Shared with Monitor service VM

 

1,000 - 2,000 Concurrent Sessions

 

Component Name

#of CPU Cores

RAM (GB)

Notes

Real-time Console

1

4

Per console instance

Monitor Service

2

8

 

Data Collector

N/A

N/A

Shared with Monitor service VM

 

2,000 - 5,000 Concurrent Sessions

 

Component Name

#of CPU Cores

RAM (GB)

Notes

Real-time Console

2

4

Per console instance, Process on demand

Monitor Service

4

12

 

Data Collector

2

4

Dedicated VM

 

5,000 - 20,000 Concurrent Sessions

 

Component Name

#of CPU Cores

RAM (GB)

Notes

Real-time Console

2

4

Per console instance, Process on demand

Monitor Service

4

16

 

Data Collector

2

8

Dedicated VM

 

20,000 + Concurrent Sessions

Please contact ControlUp Support services for guidelines on configuring environments with more than 20,000 concurrent sessions

 

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.

 

0 - 500 VDI Concurrent Sessions

 

Component Name

#of CPU Cores

RAM (GB)

Notes

Real-time Console

1

2

Per console instance

Monitor Service

2

4

 

Data Collector

N/A

N/A

Shared with Monitor service VM

 

500 - 2,000 VDI Concurrent Sessions

 

Component Name

#of CPU Cores

RAM (GB)

Notes

Real-time Console

2

4

Per console instance, Process on demand

Monitor Service

4

16

 

Data Collector

2

4

Dedicated VM

 

2,000 - 5,000 Concurrent Sessions

 

Component Name

#of CPU Cores

RAM (GB)

Notes

Real-time Console

2

8

Per console instance, Process on demand

Monitor Service

6

24

 

Data Collector

2

8

Dedicated VM

 

5,000+ VDI Concurrent Sessions

 

Please contact ControlUp Support services for guidelines on configuring environments with more than 5,000 VDI Endpoints.

 

On-premises components

 

  • On-premises server
  • IOP
  • SQL database

 

Component Name

#of CPU Cores

RAM (GB)

Notes

On Premise Server

2

8

 

Insights OP server

2 x 6 cores of 2+ GHz

12

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

 

Component Name

Disk Size

I/O

Notes

SQL Server mode #1

10gb

 

 

SQL server is used for Incidents & SBAs (mode #1) plus Insights data (mode #2)

 

 

 

Powered by Zendesk