System Details - Endpoint Test
This test collects various metrics pertaining to the CPU and memory usage of every processor supported by each Dell Wyse thin client.
Target of the test : Dell Wyse Client Group
Agent deploying the test : A remote agent
Outputs of the test : One set of results for every combination of Dell Wyse thin client:processor
Parameter | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
The nick name of the Dell Wyse Client Group component for which this test is to be configured. |
Port |
Refers to the port at which the specified host listens to. By default, this is NULL. |
Inside View Using |
To obtain the 'inside view' of performance of the Dell Wyse thin clients - i.e., to measure the internal performance of the Dell Wyse thin clients - this test uses a light-weight VM Agent software deployed on each of the Dell Wyse thin clients. The VM Agents collect performance metrics from the Dell Wyse thin clients and communicate the metrics to the eG remote agent using TCP protocol. Accordingly, by default, this parameter is set to eG VM Agent. |
Report By User |
Since this test runs for an 'Dell Wyse Client Group' component, this flag is set to No by default. |
Report Powered OS |
Since this test runs for an 'Dell Wyse Client Group' component, this flag is set to Yes by default. |
Is Cloud VMs |
Since this test runs for an 'Dell Wyse Client Group' component, this flag is set to Yes by default. |
Exclude |
Against this parameter, you can provide a comma-separated list of disk partitions that you want to exclude from the scope of monitoring. For example, you can use this parameter to exclude temporary disk partitions that the target Dell Wyse thin client creates from monitoring. By default, this parameter is set to none indicating that all the system processes will be considered for monitoring by eG Enterprise. |
CPU Utilization in Percent |
Specify the percentage of time beyond which the test should reveal the detailed diagnosis for the CPU utilization measure. By default, this parameter is set to 25. However, you can override this value as per your requirement. |
DD Frequency |
Refers to the frequency with which detailed diagnosis measures are to be generated for this test. For instance, if you set to 1:1, it means that detailed measures will be generated every time this test runs, and also every time the test detects a problem. |
Detailed Diagnosis |
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:
|
Measurements made by the test
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
CPU utilization |
This measurement indicates the percentage of CPU utilized by this processor. |
Percent |
A high value could signify a CPU bottleneck. The CPU utilization may be high because a few processes are consuming a lot of CPU, or because there are too many processes contending for a limited resource. The detailed diagnosis of this test reveals the top-10 CPU-intensive processes on the Dell Wyse thin client. |
System CPU utilization |
Indicates the percentage of CPU time spent by this processor for system-level processing. |
Percent |
An unusually high value indicates a problem and may be due to too many system-level tasks executing simultaneously. |
Run queue length |
Indicates the instantaneous length of the queue in which threads are waiting for this processor cycle. This length does not include the threads that are currently being executed. |
Number |
A value consistently greater than 2 indicates that many processes could be simultaneously contending for the processor. |
Blocked processes |
Indicates the number of processes blocked in this processor for I/O, paging, etc. |
Number |
A high value could indicate an I/O problem on the Dell Wyse thin client (e.g., a slow disk). |
Swap memory |
Denotes the committed amount of virtual memory in this processor. This corresponds to the space reserved for virtual memory on disk paging file(s). |
MB |
An unusually high value for the swap usage can indicate a memory bottleneck. Check the memory utilization of individual processes to figure out the process(es) that has (have) maximum memory consumption and look to tune their memory usages and allocations accordingly. |
Free memory |
Indicates the free memory available in this processor. |
MB |
This measure typically indicates the amount of memory available for use by applications running on the target Dell Wyse Client Group. |
Scan rate |
Indicates the memory scan rate for this processor. |
Pages/Sec |
A high value is indicative of memory thrashing. Excessive thrashing can be detrimental to the Dell Wyse thin client performance. |
Steal time |
Indicates the percentage of time, this virtual processor waits for a real CPU while the hypervisor is servicing another virtual processor. |
Percent |
This measure is applicable only for the Windows VMs that are provisioned via a VMware vSphere ESX. A low value is desired for this measure. A high value for this measure indicates that a particular virtual processor is waiting longer for real CPU resources. If this condition is left unattended, it can stall the tasks performed by the virtual processor and cause the overall performance of the virtual processor to deteriorate significantly and badly impact user-experience with the target server. The impact of stolen CPU always manifests in slowness but can have more profound effects on your infrastructure. Here are some examples: Slower page load times Slower database query times Slower processing of reports Increased queue size of asynchronous tasks because of an inability to process them quickly Increased IaaS bill due to launching more servers to handle the same amount of load To avoid such eventualities, administrators should either immediately terminate the virtual machine and launch a replacement or upgrade the VM to have more CPU. |
Note:
For multi-processor systems, where the CPU statistics are reported for each processor on the system, the statistics that are system-specific (e.g., run queue length, free memory, etc.) are only reported for the "Summary" descriptor of this test.