User Experience by Delivery Groups Test

Compare the value of this measure across delivery groups to know which group is running out of CPU resources.

A value close to 100% is a cause for concern, as it indicates that one/more users in a delivery group are consuming the group's CPU resources excessively.

A consistent increase in the handle count over a period of time is indicative of malfunctioning of programs. Compare this value across delivery group to know which group has users using a lot of handles.

Comparing these values across users will reveal which delivery group is sending/receiving bandwidth-intensive sound/audio files over the ICA channel. To minimize bandwidth consumption, you may want to consider disabling client audio mapping.

Comparing these values across users will reveal which delivery group's COM ports are sending/receiving bandwidth-intensive data over the ICA channel.

Comparing the values of these measures across delivery groups will reveal which delivery group's users are performing bandwidth-intensive file operations over the ICA channel.

If bandwidth consumption is too high, you may want to consider disabling client drive mapping on the client device. Client drive mapping allows users logged on to a virtual desktop from a client device to access their local drives transparently from the ICA session. Alternatively, you can conserve bandwidth by even refraining from accessing large files with client drive mapping over the ICA connection.

Comparing the values of these measures across delivery groups will reveal which delivery group has been transmitting/receiving bandwidth-intensive flash data.

Comparing the values of these measures across delivery groups to reveal which delivery group has been transmitting/receiving bandwidth-intensive PN traffic.

These metrics measure the collective I/O activity (which includes file, network and device I/O's) generated by all the processes being executed on a delivery group.

Comparison across delivery groups helps identify the group which is running the most I/O-intensive processes.

Ideally, the deviation in latencies over a session should be minimum so as to provide a consistent experience for the user.

A consistently high latency may be indicative of performance degradations with the machines in a delivery group. Possible reasons for an increase in latency could be increased network delays, network congestion, machine slow-down, too many simultaneous users on the machines etc. Typically, latencies will be below 5 secs.

This value indicates the percentage of memory resources that are used up by users of a delivery group. By comparing this value across delivery groups, an administrator can identify the delivery groups that are rapidly running out of physical memory resources.

A value of 0 indicates that no users are currently connected to the delivery group.

Comparing the values of these measures across delivery groups will reveal which group is issuing bandwidth-intensive print commands over the ICA channel. If bandwidth consumption is too high, you may want to consider disabling printing. Alternatively, you can avoid printing large documents over the ICA connection.

Comparing the values of these measures across delivery groups will reveal which group has been transmitting/receiving bandwidth-intensive data channel traffic.

Comparing the values of these measures across delivery groups will reveal which group has been transmitting/receiving bandwidth-intensive flash v2 data.

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 delivery groups to figure out which delivery groups are causing most page faults.

Comparison across delivery groups reveals the delivery groups that are running out of virtual memory.

The Average CPU usage of user's sessions measure averages out the total CPU usage of a delivery group on the basis of the number of processors. For instance, if the machines in a delivery group are using a total of 8 CPU cores and the total CPU usage across all user sessions on that delivery group amounts to 80%, then the value of the Average CPU usage of user's sessions measure for that delivery group 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 Average CPU usage of user's sessions 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, and other 7 processors in the 8-core processor environment are idle, the Average CPU usage of user's sessions measure will still report CPU usage as 10%. This may cause administrators to miss out on the fact that a particular processor is being over-utilized! In such environments therefore, its best to use the this measure! By reporting the total CPU usage of a delivery group across all user sessions and across all the processors the machines in that delivery group support, this measure serves as the true indicator of the level of CPU usage by a delivery group in dynamic environments. For instance, in the example above, the Average CPU time used by user's sessions of a delivery groupn 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 Average CPU usage user's sessions measure to know what CPU-intensive activities are being performed by the user.

Compare the value of this measure across delivery groups to know which delivery group is consuming the maximum bandwidth when handling HDX traffic.

Typically, ICA traffic is comprised of many small packets, as well as a some large packets. Large packets are commonly generated for initial session screen paints and printing jobs, whereas the ongoing user session is principally comprised of many small packets. For the most part, these small packets are the highest priority ICA data called Thinwire. Thinwire incorporates mouse movements and keystrokes.

Compare the value of these measures across delivery groups to know which delivery group's thinwire traffic is generating bandwidth-intensive traffic.

Compare the value of these measures acrossdelivery groups to know which delivery group is accessing bandwidth-intensive applications that are not in a session window.

Comparing the values of these measures across delivery groups will reveal which delivery group has been transmitting/receiving bandwidth-intensive multimedia traffic.

This measure should be maintained in a permissible range. A sudden rise or fall of this measure could be a cause of concern.

By comparing the value of this measure across delivery groups, you can identify the delivery group that is hogging the resources.

The Framehawk virtual channel optimizes the delivery of virtual desktops and applications to users on broadband wireless connections, when high packet loss or congestion occurs.

Note:

This measure will report the value 0 if Framehawk is not enabled for the user sessions on this delivery group or if the device from which the user is accessing the application does not support Framehawk.

This is a good measure of the effectiveness of Framehawk in optimizing the bandwidth usage over the virtual delivery channel. A low value is desired for this measure.

Note:

This measure will report the value 0 if Framehawk is not enabled for any user of the delivery group or if the device from which the user is accessing the delivery group does not support Framehawk.

This measure will report the value 0 if Framehawk is not enabled for any user of the delivery group or if the device from which the user is accessing the delivery group does not support Framehawk.

This measure will report the value 0 if Framehawk is not enabled for any user of the delivery group or if the device from which the user is accessing the delivery group does not support Framehawk.