DCV Server Processes By Users Test

In AWS AppStream environment where a DCV server is deployed on the AWS AppStream host, multiple processes that support the Amazon DCV protocol and other related services would be running on the target host. The AWS AppStream host is shared among multiple users so when the applications/desktops are streamed to the users, a large number of processes run in the background to support the streaming operation. If one of the processes utilizes the resources excessively on the target host, it will impact running of the other processes as well. To prevent such anomalies, administrators should continuously monitor the processes running on the target host. This can be easily done using the DCV Server Processes By Users test.

This test auto-discovers the processes running on the target host during a user session and report the utilization of CPU and physical and virtual memory by each process. In addition, this test also reports the number of handles, threads and GDI User interface objects used to run each process. These details help administrators to quickly find out if any process is using the resources excessively and take necessary actions to solve the issues.

Target of the test : An AWS AppStream Multi-session Host

Agent deploying the test : An internal agent

Outputs of the test : One set of results for each process:user pair on the target host

Configurable parameters for the test

Parameters	Description
Test Period	How often should the test be executed.
Host	The host for which the test is to be configured.
Port	The port at which the target host listens.
Report Total	By default, this flag is set to No. If set to Yes, then the test will report measures for only a Total descriptor. For this descriptor, the test will report the aggregate resource usage across all users to the Citrix server. The default setting of the flag on the other hand, implies that the test reports a set of metrics for each connection established by each user to the target host, by default.
Report Server

Measurements made by the test

Measurement	Description	Measurement Unit	Interpretation
CPU utilization	Indicates the percentage of CPU resources consumed by this process running in this user's session.	Percent	Compare the value of this measure across the processes to find out which process is using maximum CPU resources.
GDI objects	Indicates the number of GDI objects used by this process.	Number	A high value for this measure indicates that the process is utilizing excessive memory.
Handle count	Indicates the number handles opened by this process during the last measurement period.	Number	Compare the value of this measure across the processes to determine which process has opened more number of handles to execute. By closely tracking the handle usage of each process over time, you can identify potential handle leaks.
Physical memory	Indicates the amount of physical memory utilized by this process.	MB	A low value is desired for this measure.
Thread count	Indicates the number handles used for executing this process.	Number	Compare the value of this measure across the processes to determine which process is using more number of threads to execute.
User interface objects	Indicates the number of GDI objects used by this process.	Number
Virtual memory	Indicates the amount of virtual memory utilized by this process.	MB	A low value is desired for this measure.