Configuration of IGELOSMemoryTest

This test reports statistics related to the usage of physical memory of each of the IGEL Endpoints.

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.

• In the HOST text box, specify the HOST for which this test is to be configured.

• In the PORT text box, specify the port at which the specified host listens.

• To obtain the ‘inside view’ of performance of the IGEL Endpoints - i.e., to measure the internal performance of the IGEL Endpoints - this test uses a light-weight Endpoint Agent software deployed on each of the IGEL Endpoints. The Endpoint Agents collect performance metrics from the IGEL Endpoints and communicate the metrics to the eG remote agent using TCP protocol. Accordingly, by default, INSIDE VIEW USING parameter is set to TCP.

• Since this test runs for an ‘IGEL Endpoints’ component, REPORT BY USER flag is set to Yes by default.

• Since this test runs for an ‘IGEL Endpoints’ component, REPORT POWERED OS flag is set to Yes by default.

• Since this test runs for an ‘IGEL Endpoints’ component, IS CLOUD VMS flag is set to Yes by default.

• By default, the detailed diagnosis of the Used physical memory measure of this test reports the number of instances of each process running on the VM, and the aggregated memory usage (in MB and %) of every process across all its instances. For example, if users to a VM are together having 15 instances of Chrome open on the machine at around the same time, then the detailed diagnosis of the Used physical memory measure will compute and display the collective memory usage of all 15 instances against the Application Name, Chrome. From this, you can quickly identify the exact process that is ‘collectively’ (i.e., across its instances) over-utilizing the memory. Sometimes, 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 Chrome example above, say 8 of the 15 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 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.

• By default, MEMORY UTILIZATION IN PERCENT parameter is set to 75 percentage indicating that by default this test will display top-10 memory intensive processes on a VM in the detailed diagnosis of the Physical memory utilized measure only when the memory utilization reaches/exceeds 75 percentage. On the other hand, if the memory utilization is lower than the value specified against this parameter, then, this test displays only topv3 memory intensive processes in the detailed diagnosis of the Physical memory utilized measure so as to conserve storage space on the database. However, this setting can be overridden if required.

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

• To make diagnosis more efficient and accurate, eG 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, by default, for a particular server, choose the On option against DETAILED DIAGNOSIS. 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 bad and normal 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 button will appear in this page. Clicking on this button 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.