Default Parameters for VmgUserInDelayTest

One of the most difficult problems to diagnose by the administrators on physical desktops is the poor performance of the applications installed. Traditionally, diagnosis was done by collecting CPU, memory, disk I/O and a few other metrics. The data collected from traditional metrics were not sufficient to figure out the root cause of poor performance of the applications on the physical desktop since the variations measured by the metrics were large. Let's say, the user input (e.g. keyboard clicks and mouse clicks) sits in the input queue on the physical desktop host for longer duration until the input is picked up for processing by an application’s message queue. In such a case, the User Input Delay starts increasing because the physical desktop is under load, it means the slowness has been introduced on the physical desktop (and is not due to the network). This could be a sign that user experience is degrading to the point where administrators might want to add more hosts or increase the instance size of your hosts. Therefore, it is necessary for administrators to measure the user input flows or rather user input delays while the applications are being accessed. This can be easily measured using the VmgUserInDelayTest.

This test captures such user input delays at each physical desktop and reports the same to the administrators. With the help of this test, administrators can determine the maximum and average time taken by the applications to respond to the user input at the physical desktop, and thus figure out if there is any time delay in responses from applications. In addition, these metrics help administrators to differentiate desktop-side issues from network issues.

This page depicts the default parameters that need to be configured for the VmgUserInDelayTest.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• 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, INSIDE VIEW USING parameter is by default set to eG VM Agent.

• The REPORT POWERED OS 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 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.

• IS CLOUD VMs 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.

• The 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.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.