eG Monitoring
 

Measures reported by WVDWinProcessTest

The WVDWinProcessTest reports additional statistics pertaining to processes running on the chosen Session Host / Azure Virtual Desktop.

Outputs of the test : One set of results for each network interface on the chosen Session Host / Azure Virtual Desktop.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Num_procs_running Indicates the number of processes that are currently running. Number  
Handle_count Indicates the number of handles opened by the process. Number An increasing trend in this measure is indicative of a memory leak in the process.
No_of_threads Indicates the number of threads that are used by the process. Number  
Virtual_memory_used Indicates the amount of virtual memory that is being used by the process. MB  
IO_data_rate Indicates the rate at which processes are reading and writing bytes in I/O operations. Kbytes/Sec This value counts all I/O activity generated by each process and includes file, network and device I/Os.
IO_data_oper_rate Indicates the rate at which the process is issuing read and write data to file, network and device I/O operations. Operations/Sec  
IO_read_data_rate Indicates the rate at which the process is reading data from file, network and device I/O operations. Kbytes/Sec  
IO_write_data_rate Indicates the rate at which the process is writing data to file, network and device I/O operations. Kbytes/Sec  
Page_fault_rate Indicates the total rate at which page faults are occurring for the threads of all matching processes. Faults/Sec A page fault occurs when a thread refers to a virtual memory page that is not in its working set in main memory. This may not cause the page to be fetched from disk if it is on the standby list and hence already in main memory, or if it is in use by another process with whom the page is shared.
Working_set Indicates the current size of the working set of a process. MB The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed they will then be soft-faulted back into the Working Set before leaving main memory. If a process pattern matches multiple processes, the memory working set reported is the sum of the working sets for the processes that match the specified pattern. Detailed diagnosis for this test provides details of the individual processes and their individual working sets.

Comparing the working set across processes indicates which process(es) are taking up excessive memory.

By tracking the working set of a process over time, you can determine if the application has a memoryleak or not.