| Measurement |
Description |
Measurement Unit |
Interpretation |
| No_of_sessions |
Represents the current number of sessions for a particular user |
Number |
A value of 0 indicates that the user is not currently connected to the VMware View RDS server. You can use the detailed diagnosis of this measure to know which applications are currently run by a user and the resource usage of each application. Resource-hungry applications can thus be identified. |
| Cpu_util |
The CPU utilization for a session is the percentage of time that all of the threads/processes of a user session used the processor to execute instructions. If a user is connected via multiple sessions, the value reported is the sum of all CPU utilizations across all the sessions. |
Percent |
This value indicates the percentage of CPU resources that are used by applications run by this user. Excessive CPU usage by a user can impact performance for other users. Check the detailed diagnosis to view the offending processes/applications. |
| Mem_util |
This value represents the ratio of the resident set size of the memory utilized by the user to the physical memory of the host system, expressed as a percentage. If a user is connected via multiple sessions, the value reported is the sum of all memory utilizations across all the sessions. |
Percent |
This value indicates the percentage of memory resources that are used up by a specific user. By comparing this value across users, an administrator can identify the PCoIP sessions that are engaged in memory-intensive processing on the VMware View RDS server. Check the detailed diagnosis to view the offending processes/applications. |
| Input_bandwidth |
Indicates the average bandwidth used for client to server communications for all the sessions of a user. |
KB/Sec |
|
| Input_errors |
The average number of input errors of all types for all the sessions of a user. Example: Lost ACK's, badly formed packets, etc. |
Errors/Sec |
|
| Output_bandwidth |
Indicates the average bandwidth used for server to client communications for all the sessions of a user |
KB/Sec |
|
| Output_errors |
The average number of output errors of all types for all the sessions of a user. Example: Lost ACK's, badly formed packets, etc. |
Errors/Sec |
|
| IO_reads |
Indicates the rate of I/O reads done by all processes being run by a user. |
KBps |
These metrics measure the collective I/O activity (which includes file, network and device I/O's) generated by all the processes being executed by a user. When viewed along with the system I/O metrics reported by the DiskActivityTest test, these measures help you determine the network I/O. Comparison across users helps identify the user who is running the most I/O-intensive processes. Check the detailed diagnosis for the offending processes/applications. |
| IO_writes |
Indicates the rate of I/O writes done by all processes being run by a user. |
KBps |
| Page_faults |
Indicates the rate of page faults seen by all processes being run by a user. |
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 which user is causing most page faults. |
| Virtual_memory |
Indicates the total virtual memory being used by all processes being run by a user. |
MB |
Comparison across users reveals the user who is being a drain on the virtual memory space. |
| Handles |
Indicates the total number of handles being currently held by all processes of a user. |
Number |
A consistent increase in the handle count over a period of time is indicative of malfunctioning of programs. Compare this value across users to see which user is using a lot of handles. Check detailed diagnosis for further information. |
| Cpu_util_time |
Indicates the percentage of time, across all processors, this user hogged the CPU. |
Percent |
The CPU usage for user's processes measure averages out the total CPU usage of a user on the basis of the number of processors. For instance, if your VMware View RDS server is using an 8-core processor and the total CPU usage of a user across all his/her sessions amounts to 80%, then the value of the CPU usage for user's processes measure for that user will be 10 % (80/8 processors = 10). This accurately denotes the extent of CPU usage in an environment where load is uniformly balanced across multiple processors. However, in environments where load is not well-balanced, the CPU usage for user's processes measure may not be an accurate indicator of CPU usage per user. For instance, if a single processor is used nearly 80% of the time by a user, and other 7 processors in the 8-core processor environment are idle, the CPU usage for user's processes measure will still report CPU usage as 10%. This may cause administrators to miss out on the fact that the user is actually hogging a particular processor! In such environments therefore, its best to use the CPU time used by user's sessions measure! By reporting the total CPU usage of a user across all his/her sessions and across all the processors the target VMware View RDS server supports, this measure serves as the true indicator of the level of CPU usage by a user in dynamic environments. For instance, in the example above, the CPU time used by user’s sessions of the user will be 80% (and not 10%, as in the case of the CPU usage for user's processes measure). A high value or a consistent increase in the value of this measure is hence serious and demands immediate attention. In such situations, use the detailed diagnosis of the CPU usage for user’s processes measure to know what CPU-intensive activities are being performed by the user. |
| Gen_RX_bandwidth |
Indicates the rate at which data was received by this user from the server. |
Kbit/Sec |
Comparing the value of each of these measures across users will enable administrators to quickly and accurately identify users who are consuming the maximum bandwidth. Once you zero-in on the user, you can compare the Gen_RX_bandwidth of that user with the Gen_TX_bandwidth to know when the user consumed more bandwidth - when receiving data or while sending data? |
| Gen_TX_bandwidth |
Indicates the rate at which data was sent by this user to the server. |
Kbit/Sec |
| Audio_RX_bandwidth |
Indicates the bandwidth used while transmitting sound/audio to this user. |
Kbit/Sec |
Comparing these values across users will reveal which user is sending/receiving bandwidth-intensive sound/audio files over PCoIP. |
| Audio_TX_bandwidth |
Indicates the bandwidth used while receiving sound/audio from this user. |
Kbit/Sec |
| Img_RX_bandwidth |
Indicates the bandwidth used when sending imaging data to this user. |
Kbit/Sec |
Comparing these values across users will reveal which user is sending/receiving bandwidth-intensive images over PCoIP. |
| Img_TX_bandwidth |
Indicates the bandwidth used when receiving imaging data from this user. |
Kbit/Sec |
| Decoder_capability |
Indicates the current estimate of the decoder processing capability. |
Kbit/Sec |
|
| Net_RX_bandwidth |
Indicates the overall bandwidth consumed by the packets received by this user. |
Kbit/Sec |
Comparing the values of these measures across users will reveal which user is performing bandwidth-intensive operations over the PCoIP channel. |
| Net_TX_bandwidth |
Indicates the overall bandwidth consumed by PCoIP packets sent by this user. |
Kbit/Sec |
| USB_RX_bandwidth |
Indicates the bandwidth used when this user received USB data over the PCoIP channel. |
Kbit/Sec |
Comparing the values of these measures across users will reveal which user is sending/receiving bandwidth-intensive USB data over the PCoIP channel. |
| USB_TX_bandwidth |
Indicates the bandwidth used when this user sent USB data over the PCoIP channel. |
Kbit/Sec |
| Gen_Sent_packet_lost |
Indicates the number of PCoIP packets lost by this user during transmission. |
Number |
Ideally, the value of this measure should be 0. |
| Gen_received_packet_lost |
Indicates the number of PCoIP packets lost by this user during reception. |
Number |
Ideally, the value of this measure should be 0. |
| Net_Received_packet_lost |
Indicates the percentage of packets received by this user that were lost. |
Percent |
A high value for these measures is indicative of a bad network connection between the user terminal and the virtual desktop. |
| Net_TX_packet_lost |
Indicates the percentage of packets transmitted by this user that were lost. |
Percent |
| Encoded_frame |
Indicates the number of imaging frames that were encoded per second. |
Frames/Sec |
|
| Net_round_trip |
Indicates the round trip latency between the server and this user terminal. |
Seconds |
Comparing the value of this measure across users will enable administrators to quickly and accurately identify users who are experiencing higher latency when connecting to the RDS server. |
| Session_duration |
Indicates the total time for which this user's session was open on the server. |
Seconds |
Compare the value of this measure to know which user was logged into the server for the maximum time. |