Product Documentation

Performance overview

May 21, 2017

Generally speaking, Citrix SCOM Management Pack for XenApp and XenDesktop consists of three parts:

  • The part installed on the SCOM management server (mandatory)
  • Citrix SCOM Management Pack Agent for XenApp and XenDesktop (mandatory)
  • Citrix SCOM Management Pack Machine Agent for XenApp and XenDesktop (optional)

The SCOM management server-side part

This part is a collection of management packs include discoveries, monitors, rules, tasks, and reports. From the compute and memory perspective, this part does not significantly add to the basic resource requirements of SCOM management server itself. It is not resource-intensive in terms of storage requirements of the SCOM reporting data warehouse database. For these reasons, there are no special considerations related to the SCOM management-server part when monitoring larger Citrix XenApp and XenDesktop environments.

Citrix SCOM Management Pack Agent for XenApp and XenDesktop

Performance and resource consumption of Citrix SCOM Management Pack Agent for XenApp and XenDesktop primarily depend on the size of your XenApp and XenDesktop environment, specifically on the number of resources within each Site. Furthermore, they are influenced by the load on the Delivery Controller instances. In contrast, the number of Sites in your XenApp and XenDesktop environment has no influence on the performance and resource consumption.

For scaling up Citrix SCOM Management Pack Agent for XenApp and XenDesktop, hardware of the hosting Delivery Controller must be reconfigured. The Agent cannot be scaled out.

Citrix SCOM Management Pack Machine Agent for XenApp and XenDesktop

The product's Machine Agent can be scaled up without the need of altering XenApp and XenDesktop deployment, as no XenApp and XenDesktop component is installed on its proxy node. Machine Agent can also be scaled out; you can achieve this by installing multiple instances on multiple proxy nodes and configuring it such that each Machine Agent instance handles only a subset of all Delivery Controller instances.
Note: The machine agent is not tested for scale or performance.

Configuration specifications

All figures in this document are valid for environments that:

  • Are monitored with the specified product version of Citrix SCOM Management Pack for XenApp and XenDesktop
  • Match the documented configuration specifications for XenApp and XenDesktop and SCOM
  • Use the default configuration of management packs in terms of which rules and monitors are enabled (this applies to management packs included in Citrix SCOM Management Pack for XenApp and XenDesktop and management packs bundled with SCOM). In addition:
    • Disable VDA service monitoring
    • Enable connectors when the environment contains more than 600 Server OS machines. For more information on configuring connectors, see Configuring SCOM Administrator.
  • Use the default configuration of SCOM management server and SCOM agents, without fine-tuning or any special adjustment.

For the product to work with the scale of the environment documented here, it is recommended that you configure the SCOM agent on all controllers. For environments with approximately 15,000 VDAs and/or around 25,000 sessions (Desktop OS and Server OS) or more, follow the recommended configuration steps in Configuration for monitoring large XenApp and XenDesktop environments.

Validated Citrix SCOM Management Pack for XenApp and XenDesktop version

Validation of Citrix SCOM Management Pack for XenApp and XenDesktop was performed with the product version listed in the following table.

Product Version
Citrix SCOM Management Pack for XenApp and XenDesktop 3.12


Citrix XenApp and XenDesktop configuration specification

With this configuration, the Site database server is deployed outside the Delivery Controller computer. 

Computer: Delivery Controller
Specification item Value
Compute four virtual CPUs; CPU clock speed of 2.67 GHz
Memory 16 GB of RAM
Software version Citrix XenApp and XenDesktop 7.13

 

Computer: Site database server
Specification item Value
Compute four virtual CPUs; CPU clock speed of 2.67 GHz
Memory 24 GB of RAM
Software version  Microsoft SQL Server 2014 R2

Microsoft System Center Operations Manager configuration specification

With this configuration, the SCOM database and data warehouse server is deployed outside the SCOM management server computer.

Computer: SCOM management server
Specification item Value
Compute eight virtual CPUs; CPU clock speed of 2.67 GHz
Memory 16 GB of RAM
Software version Microsoft System Center Operations Manager 2012 R2

 

Computer: SCOM database and data warehouse server
Specification item Value
Compute eight virtual CPUs; CPU clock speed of 2.67 GHz
Memory 24 GB of RAM
Software version Microsoft SQL Server 2014 R2

 

Computer: SCOM reporting database
Specification item Value
Compute four virtual CPUs; CPU clock speed of 2.67 GHz
Memory 8 GB of RAM
Software version Microsoft SQL Server 2014 R2

Monitoring ability

The following table lists the maximum values at which the Citrix SCOM Management Pack for XenApp and XenDesktop was successfully validated. The product might be able to monitor environments larger than stated below. However, this hasn't been tested.

Maximum number of monitored items (per Site)

 Item Value
Delivery groups 300
Server OS machines 2000
Server OS machines in a delivery group 200
Desktop OS machines 36,000
Applications 2,500
Concurrent sessions 68,000 (36,000 Desktop OS sessions + 32,000 Server OS sessions)

Average resource consumption

Resource consumption was measured in a XenApp and XenDesktop Site with four Delivery Controller instances. Measurement was made on the Delivery Controller where Citrix SCOM Management Pack Agent for XenApp and XenDesktop did most data processing. Measuring spanned a period of 2.5 days. Windows Performance Monitor was used as the measuring tool.

Important: In XenApp and XenDesktop deployments with multiple Delivery Controller instances, the majority of data processing is performed by a single instance of Citrix SCOM Management Pack Agent for XenApp and XenDesktop (on one Delivery Controller). Resource consumption is documented only for the primary controller, as the other controllers in the site have minimal resource usage.

Average consumption on a Delivery Controller (for 20,600 VDIs)

Item Value
MPXAXDAgent CPU usage1 10.62%
HealthService CPU usage 1.90%
MonitoringHost CPU usage
3.88%
MPXAXDAgent memory usage 1480 MB
HealthService memory usage 174 MB
MonitoringHost memory usage 240 MB

1 CPU usage is calculated based on the % Processor Time counter and the number of processor cores or virtual CPUs.

The number of published applications has a negligible effect on the CPU usage of the MPXAXDAgent service.

The following figure shows changes in CPU usage of MPXAXDAgentHealthService and MonitoringHost after these services had been started for the first time. Values are taken from the first part of the entire measurement time period (first four hours), when initial high data inflow loaded compute resource substantially. After first three hours, initial high load decreased significantly.

localized image

The following figure shows typical patterns of changes in CPU usage of MPXAXDAgentHealthService and MonitoringHost through a major part of the measurement time period, after the initial high load had already subsided. The measurement was made in the validation set 2 (VS2; see figure for memory usage).

localized image

As the figure above shows, bursts of high CPU usage of MPXAXDAgent occured every five minutes, while spikes of high CPU usage of HealthService and MonitoringHost were not periodical. 

The following figure shows the memory usage of MPXAXDAgent, and HealthService, and MonitoringHost through time, measured during the whole validation set.

localized image

As the figure above shows, on the Delivery Controller there should be approximately 4.2 GB of physical memory available for the joint needs of the MPXAXDAgentHealthService and MonitoringHost services.