Configuration of WVDOSMemoryTest

This test reports statistics related to the usage of physical memory of the VMs.

The default parameters associated with this test are as follows:

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

• In the HOST text box, the IP address of the host for which the test is to be configured has to be specified.

• Specify the port at which the specified HOST listens to in the PORT text box. By default, this is NULL.

• By default, the detailed diagnosis of the Used memory measure of this test reports the number of instances of each process running on the virtual desktop, and the aggregated memory usage (in MB and %) of every process across all its instances. For example, if users to a virtual desktop are together having 15 instances of Internet Explorer open on the desktop at around the same time, then the detailed diagnosis of the Used memory measure will compute and display the collective memory usage of all 15 instances against the Application Name, Internet Explorer. From this, you can quickly identify the exact process that is ‘collectively’ (i.e., across its instances) over-utilizing the desktop memory. In a multi-user environment such as Azure virtual desktops, administrators might want to isolate not just the process, but also similar process arguments that are guilty of abnormal memory consumption. This granular insight will take administrators closer to the root-cause of the memory bottleneck on a desktop. For instance, in the Internet Explorer example above, say 8 of the 15 IE instances are used to access the same YouTube video, and 7 instances are accessing a shopping site. In such a case, if memory usage is aggregated at the URL-level and not the process-level, then administrators can quickly identify which precise URL is draining desktop memory-the YouTube video? or the shopping site? For this, detailed diagnostics should be grouped by process arguments (eg., URLs) and not just by process/application names. To enable grouping by arguments, set the Group Processes With Arguments flag to Yes. By default, this flag is set to No.

• To make diagnosis more efficient and accurate, the eG suite 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.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

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

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.