Configuration of VmgGPUAdapterTest

A graphics processing unit (GPU) adapter (also known as video card, graphics card, and video adapter) is a discreet card connected to one or more physical/physical machines. The GPU adapter contains video RAM and a GPU chip and renders real-time 2D and 3D graphics applications, images, animations and video by performing rapid mathematical calculations. To perform such calculations at higher speed, the GPU adapter should be allocated with adequate memory on the physical machine. Inadequate memory allocation and inefficient utilization of the GPU adapter can affect the processing of intensive tasks related graphics on the physical machines, which in turn can adversely impact the performance of the applications operating on the VMs. Therefore, it is imperative that administrators should closely observe how well the GPU adapter uses the allocated and shared memory available to it. This way, a potential memory crunch can be proactively detected. This can be achieved with the help of the VmgGPUAdapterTest.

The test auto-discovers the GPU adapters connected to each physical machine on the physical server and for each GPU adapter, reports the statistics related to memory utilization. This test also reveals how well the GPU is utilized for performing different tasks such as video decoding, processing 3D frames, etc. These metrics help administrators to judge whether/not adequate memory is available for use by the GPU adapters and identify the GPU adapter that is running out of memory.

The default parameters associated with this test are:

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

• Specify the nick name of the target component for which this test is to be configured in the HOST text box.

• Indicate the port at which the host listens to in the PORT text box. By default, this is NULL.

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

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

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