Client Network Performance Test

High network latencies, poor signal strength, or packet losses during transmission can cause significant slow-downs in request processing by the desktop. Hence, monitoring latencies between the physical desktops and client terminals that are used by users of the physical desktops is important.

Using this test, an administrator can identify the users whose sessions are being impacted by high latencies or by excessive packet drops. In some cases, a physical desktop may regard a user session as active, even though the network link connecting the user terminal to the physical desktop has failed. The Client Network Performance test alerts administrators to such situations. In addition, if the physical desktop is connected to a WiFi network, this test also reports the signal strength and quality of WiFi network accessed by the,/ physical desktops.

Note:

This test will report metrics only if the desktop is connected to the internet.

Target of the test : A Physical Desktop Group

Agent deploying the test : A remote agent

Outputs of the test : One set of outputs for every user currently connected to the physical desktop

Configurable parameters for the test
Parameter	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 specified host listens. By default, this is NULL
Inside View Using	To obtain the 'inside view' of performance of the desktops - i.e., to measure the internal performance of the physical desktops - this test uses a light-weight eG VM Agent software deployed on each of the desktops. Accordingly, this parameter is by default set to eG VM Agent.
Report Powered OS	This flag is relevant only for those tests that are mapped to the Physical Desktops Details layer. If this flag is set to Yes (which is the default setting), then the 'inside view' tests will report measures for even those physical desktops that do not have any users logged in currently. Such desktops will be identified by their name and not by the username_on_physicalmachinename. On the other hand, if this flag is set to No, then this test will not report measures for those physical desktops to which no users are logged in currently.
Report By User	This flag is set to Yes by default. This implies that the physical machines in environments will always be identified using the login name of the user. In other words, this test will, by default, report measures for every username_on_physicalmachinename.
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test

Measurement

Description

Measurement Unit

Interpretation

Total devices connected to local router

Indicates the number of physical desktops connected to the local router.

Number

This measure is only applicable for Summary descriptor.

Wi-Fi signal strength

Indicates the signal strength of the WiFi network accessed by the physical desktop.

This measure will be reported only when the physical desktop is connected to a WiFi network.

By default, the eG VM agent executes the netsh wlan show interface command on the physical desktop to determine the WiFi signal strength and the quality of the signal. eG Enterprise determines the WiFi signal strength based on the signal quality range determined upon execution of the command. The table below indicates the values that this measure can report and their corresponding numeric equivalents along with the signal quality range:

Measure value	Numeric Value	Signal Quality Range
Poor	0	0
Weak	1	1%-25%
Fair	2	26%-50%
Good	3	51%-75%
Excellent	4	Above 75%

Note:

By default, this measure reports the above-mentioned Measure Values while indicating the Wi-Fi signal strength. However, in the graph of this measure, signal strength will be represented using the corresponding numeric equivalents only - i.e., 0 to 4.

Wi-Fi signal quality

Indicates the percentage of signal strength of the WiFi network accessed by the physical desktop.

Percent

This measure will be reported only when the physical desktop is connected to a WiFi network.

A high value is preferred for this measure.

Local router latency

Indicates the time taken by the local router to respond to the requests made from the physical desktop.

Milliseconds

A high value is a cause for concern, as it indicates a potentially latent function. The detailed diagnosis of this measure reveals the IP address of the local router.

Local router packet loss

Indicates the percentage of packets lost during data exchange between the physical desktop and the local router.

Percent

ISP latency

Indicates the time taken by the ISP (Internet Service Provider) to respond to the requests made from the physical desktop.

Milliseconds

A high value is a cause for concern, as it indicates a potentially latent function.

The detailed diagnosis of this measure reveals the IP address of the Internet Service Provider.

ISP packet loss

Indicates the percentage of packets lost during data exchange between the physical desktop and the ISP (Internet Service Provider).

Percent

Internet latency

Indicates how long the physical desktop waited to get response from internet.

Milliseconds

This metric is collected by pinging Google DNS servers. Seeing higher ping latency when pinging Google's DNS servers (e.g. 8.8.8.8) can indicate a few potential issues:

Network congestion or routing issues between your network and Google's DNS servers, resulting in increased latency. This could be due to problems with your ISP's network or the intermediate networks the traffic traverses.
Issues with your local network equipment (routers, switches, etc.) or the cabling, introducing delays in the path to Google's DNS servers.
Overloaded or under performing DNS servers within your ISP's network, adding latency before the query reaches Google's servers.

As for toleration limits and when to complain:

For general web browsing, DNS lookup times under 50ms are considered good. Between 50-150ms is acceptable but may cause slightly slower loading times. Anything over 150ms will likely result in noticeable delays when accessing websites.
For time-sensitive applications like Virtual Desktop Access, Video conferences, video streaming, online gaming, etc., DNS lookup times should ideally be under 25ms for a smooth experience. Anything over 50ms could potentially cause issues.

If you consistently experience DNS lookup times over 150ms when pinging Google's DNS servers, and other internet services are also slow, it would be reasonable to contact your ISP and report the issue, as it indicates a problem with their network or DNS infrastructure impacting your overall internet performance.

However, if the high latency is intermittent or only occurs during peak usage hours, some amount of increased latency may be expected due to network congestion and might not warrant an immediate complaint.

In summary, while some DNS latency is normal, persistent high latency over 150ms when pinging reliable DNS servers like Google's could signify an issue worth reporting to your ISP for investigation.

Internet packet loss

Indicates the percentage of packets lost during data exchange between the physical desktop and the internet.

Percent

This metric is collected by pinging Google DNS servers. Seeing packet loss or/and higher latency when pinging Google's DNS servers (e.g. 8.8.8.8) can indicate a few potential issues:

Network congestion or routing issues between your network and Google's DNS servers, resulting in increased latency and packet loss. This could be due to problems with your ISP's network or the intermediate networks the traffic traverses.
Issues with your local network equipment (routers, switches, etc.) or cabling, introducing delays and packet drops in the path to Google's DNS servers.
Overloaded or underperforming DNS servers within your ISP's network, causing latency spikes and packet loss before the query reaches Google's servers.

As for toleration limits and when to complain:

For general web browsing, DNS lookup times under 50ms are considered good, and packet loss under 1% is generally tolerable.
Between 50-150ms latency with 1-3% packet loss is poor quality and may cause noticeable delays when accessing websites.
For time-sensitive applications like video streaming, online gaming, etc., DNS lookup times should ideally be under 25ms with minimal packet loss for a smooth experience.

Latency over 50ms or packet loss over 1% could potentially cause issues. If you consistently experience DNS lookup times over 150ms with over 3% packet loss when pinging Google's DNS servers, and other internet services are also slow, it would be reasonable to contact your ISP and report the issue, as it indicates a problem with their network or DNS infrastructure impacting your overall internet performance. However, if the high latency and packet loss are intermittent or only occur during peak usage hours, some amount of increased latency and occasional packet drops may be expected due to network congestion and might not warrant an immediate complaint. In summary, persistent high latency over 150ms with over 3% packet loss when pinging reliable DNS servers like Google's could signify an issue worth reporting to your ISP for investigation.

Device Connectivity Mode

Indicates the connectivity mode of current physical desktop

The table below indicates the values that this measure can report and their corresponding numeric equivalents along with the signal quality range:

Measure value	Numeric Value
Wireless	1
Wired	2

Note:

By default, this measure reports the above-mentioned Measure Values while indicating the Connectivity Mode. However, in the graph of this measure, signal strength will be represented using the corresponding numeric equivalents only - i.e., 1 or 2.