Horizon RDS Users By Cities Test

The Omnissa Horizon RDS environment hosts a wide variety of applications that can be shared by multiple users simultaneously. Users can access those applications from different geographic locations such as countries, cities and regions at any time. While users access the applications from different geographic locations, it is the administrator's responsibility to ensure consistent user experience for all users, regardless of their geographic location. When server resources are shared by users from multiple cities, excessive resource and bandwidth utilization by users from a specific city could impact the performance of the applications for users from other cities. Therefore, it is imperative to extensively monitor the activity of users spread across each city by assessing the traffic between the server and the user terminals. For this purpose, administrators can use the Horizon RDS Users By Cities test.

This test continuously monitors the resources taken up by a user's session on the server for each city. The results of this test can be used in troubleshooting and proactive monitoring. For example, when a user from a particular city reports a performance problem, administrators can quickly check the the CPU/memory/disk usage of the user sessions from each city as well as the resource usage of user sessions from each city. The administrator also has access to details on the packet loss experienced by the user sessions from each city. This information can be used to spot a particular city from which maximum number of user sessions are established.

Target of the test : An Omnissa Horizon RDS server

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for each city from which users are accessing the Omnissa Horizon RDS server that is being monitored

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	Refers to the port used by the Omnissa Horizon RDS server.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Round trip time	Indicates the round trip latency between the users from this city and the server.	Seconds	A high value is indicative of a connection bottleneck.
Session data received	Indicates the rate at which the data was received during the user sessions from this city.	Kbps	Using the values of these measures help administrators to determine the data traffic during the session from the city and figure out the city that is handling maximum data traffic.
Session data transmitted	Indicates the rate at which the data was transmitted during the user sessions from this city.	Kbps	Session data transmitted
Packet loss	Indicates the percentage of packet loss experienced by the user sessions from this city.	Percent	A high value indicates that a large number of packets were lost without being retransmitted. By comparing the value of this measure across cities, you can find the city that has suffered the maximum data loss. This could be owing to a bad network connection between the remote user terminals from the city and the server.
Frames rate	Indicates the rate at which frames were processed during the user's sessions from this city.	Frames/sec	This measure indicates how quickly the image frames are processed during the session from the city. A lower value of this measure indicates that the frames are processed slowly which may lead to processing bottleneck.
User sessions	Indicates the number of user sessions initiated from this city.	Number
CPU usage of user processes	Indicates the percentage of CPU utilized by the processes being run by users from this city.	Percent	A high value for this measure is a cause of concern. Comparing the value of this measure across browsers helps administrators in identifying the browser that is utilizing too much of CPU resources.
Memory usage of user processes	Indicates the percentage of memory utilized by the processes being run from this city.	Percent	A high value for this measure is a cause of concern. Comparing the value of this measure across browsers helps administrators in identifying the browser that is utilizing too much of memory resources.
I/O read rate for user processes	Indicates the rate of I/O reads done by all processes being run by a user from this city.	KB/sec	Comparing these measures across different cities helps identify the city from which the most I/O-intensive processes are being run by users.
I/O write rate for user processes	Indicates the rate of I/O writes done by all processes being run by a user from this city.	KB/sec	I/O write rate for user processes
Faults for user processes	Indicates the rate of page faults seen by all processes being run by a user from this city.	Faults/sec	Page Faults occur in the threads executing in a process. A page fault occurs when a thread refers to a virtual memory page that is not in its working set in main memory. If the page is on the standby list and hence already in main memory, or if the page is in use by another process with whom the page is shared, then the page fault will not cause the page to be fetched from disk. Excessive page faults could result in decreased performance. Compare values across users to figure out the users from which city are causing most page faults.
Virtual memory of user processes	Indicates the amount of virtual memory used by the user's sessions from this city.	MB	Compare the value of this measure across cities to know the users from which city are consuming the maximum virtual memory.
I/O reads and writes for user processes	Indicates the rate of I/O reads and writes done by all processes being run by the users from this city.	KB/sec
Working set memory for user processes	Indicates the current size of the working set of processes being run by users from this city.	MB	The Working Set is the set of memory pages touched recently by the threads in a process. If free memory in the server is above a threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed they will then be soft-faulted back into the Working Set before leaving main memory. If multiple processes are running in the user's session, the memory working set reported is the sum of the working sets for all the user's processes. Comparing the working set across cities indicates which city/cities are taking up excessive memory. Check the detailed diagnosis to view the offending processes/applications.
Total user logon duration	Indicates the time taken by the users from this city to logon to the server.	Seconds	The value of this measure should be low.