ISessionPerformanceInfo Properties

Win32_PerfFormattedData_TermService_TerminalServicesSession: Total number of handles currently opened by this process. This number is the sum of the handles currently opened by each thread in this process.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of input async framing errors. These can be caused by a noisy transmission line. Using a smaller packet size may help in some cases.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of input async overflow errors. These can be caused by a lack of buffer space available on the host.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of input async overrun errors. These can be caused by the baud rate being faster than the computer can handle, or by a non-16550 serial line being used. Overruns can also occur if too many high speed serial lines are active at one time for the processor's power.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of input async parity errors. These can be caused by a noisy transmission line.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of bytes input on this session, including all protocol overhead.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of bytes input after compression. This number compared with the TotalBytes input is the compression ratio.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of input compression dictionary flushes. When the data cannot be compressed, the compression dictionary is flushed so that newer data has a better chance of being compressed. One cause of data not compressing includes transferring compressed files over client drive mappings.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Compression ratio of the server input data stream.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of input errors of all types.Some examples of input errors are lost acknowledgements(ACKs), badly formed packets, and so on.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Total number of time outs on the communication line, as seen from the client side of the connection. These are typically the result of a noisy line. On some high latency networks, this could be the result of the protocol time out being too short. Increasing the protocol time out on these types of lines improves performance by reducing needless re-transmissions.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of Terminal Services transport-level errors on input.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of times that a wait for an available send buffer was done by the protocols on the client side of the connection.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of bytes entered on this session after all protocol overhead has been removed.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of frames entered after any additional protocol-added frames have been removed.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Label by which the statistic or metric is known. When sub-classed, the property can be overridden to be a key property. This property is inherited from CIM_StatisticalInformation.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of output async framing errors. This could be caused by a hardware or line problem.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of async overflow errors produced.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of async overrun errors produced.

Win32_PerfFormattedData_TermService_TerminalServicesSession: OutputAsyncParityError Number of async parity errors produced.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of bytes produced on this session, including all protocol overhead.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of bytes produced after compression. This number compared with the TotalBytes value is the compression ratio.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of compression dictionary flushes produced.When the data cannot be compressed, the compression dictionary is flushed so that newer data has a better chance of being compressed. One cause of data not compressing includes transferring compressed files over client drive mappings.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Compression ratio of the server output data stream.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of output errors of all types. Some example output errors are lost acknowledgements (ACKs), badly formed packets, and so on.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of frames (packets) produced on this session.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Total number of time outs on the communication line from the host side of the connection. These are typically the result of a noisy line. On some high latency networks, this could be the result of the protocol time out being too short. Increasing the protocol time out on these types of lines improves performance by reducing needless re-transmissions.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of Terminal Services transport-level errors produced.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of times that a wait for an available send buffer was done by the protocol on the server side of the connection.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of bytes produced on this session after all protocol overhead has been removed.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of frames produced before any additional protocol frames have been added.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Rate at which page faults occur in the threads executing in this process. A page fault occurs when a thread refers to a virtual memory page that is not in its working set in main memory. This can cause the page not 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 which the page is shared.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Current number of bytes this process has used in the paging file(s). Paging files are used to store pages of memory used by the process that are not contained in other files. Paging files are shared by all processes, and lack of space in paging files can prevent other processes from allocating memory.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Maximum number of bytes this process has used in the paging file(s). Paging files are used to store pages of memory used by the process that are not contained in other files. Paging files are shared by all processes, and lack of space in paging files can prevent other processes from allocating memory.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Percentage of elapsed time that the threads of the process have spent executing code in privileged mode. When an- operating system service is called, the service often runs in privileged mode to gain access to system-private data. Such data is protected from access by threads executing in user mode. Calls to the system can be explicit or implicit, such as page faults or interrupts. The operating system uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. These subsystem processes provide additional protection. Therefore, some work done by the operating system on behalf of your application might appear in other subsystem processes in addition to the privileged time in your process.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Percentage of elapsed time that all of the threads of this process used the processor to execute instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Percentage of elapsed time that this process's threads have spent executing code in user mode. Applications, environment subsystems and integral subsystems execute in user mode. Code executing in user mode cannot damage the integrity of the operating system executive, kernel, and device drivers. The operating system uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. These subsystem processes provide additional protection. Therefore, some work done by the operating system on behalf of your application might appear in other subsystem processes in addition to the privileged time in your process.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of bytes in the nonpaged pool, an area of system memory (physical memory used by the operating system) for objects that cannot be written to disk, but must remain in physical memory as long as they are allocated. This property displays the last observed value only; it is not an average.

Win32_PerfFormattedData_TermService_TerminalServicesSession:Number of bytes in the paged pool, an area of system memory (physical memory used by the operating system) for objects that can be written to disk when they are not being used. This property displays the last observed value only; it is not an average.

Win32_PerfFormattedData_TermService_TerminalServicesSession:Current number of bytes this process has allocated that cannot be shared with other processes.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Hit ratio in the protocol bitmap cache. A higher bit ratio means better performance because data transmissions are reduced. Low hit ratios are due to the screen updating with new information that is either not reused or is flushed out of the client cache.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of hits in the protocol bitmap cache.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Hit ratio in the protocol brush cache. A higher hit ratio means better performance because data transmissions are reduced. Low hit ratios are due to the screen updating with new information that is either not re-used, or is flushed out of the client cache.

Win32_PerfFormattedData_TermService_TerminalServicesSession: ProtocolBrushCacheHits Number of hits in the protocol brush cache.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of hits in the protocol brush cache.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Hit ratio in the protocol glyph cache. A higher hit ratio means better performance because data transmissions are reduced. Low hit ratios are due to the screen updating with new information that is either not re-used, or is flushed out of the client cache.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of hits in the protocol glyph cache.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Hit ratio in the protocol glyph cache. A higher hit ratio means better performance because data transmissions are reduced. Low hit ratios are due to the screen updating with new information that is either not re-used, or is flushed out of the client cache.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Hit ratio in the protocol save screen bitmap cache. A higher hit ratio means better performance because data transmissions are reduced. Low hit ratios are due to the screen updating with new information that is either not re-used, or is flushed out of the client cache.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of hits in the protocol save screen bitmap cache.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of references to the protocol save screen bitmap cache.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of threads currently active in this process. An instruction is the basic unit of execution in a processor, and a thread is the object that executes instructions. Every running process has at least one thread.

Win32_PerfRawData_PerfProc_Process: Timestamp value in 100 nanosecond units.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Total number of async framing errors. These can be caused by a noisy transmission line. Using a smaller packet size may help in some cases.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Total number of async overflow errors. These can be caused by a lack of buffer space available on the host.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Total number of async overrun errors. These can be caused by the baud rate being faster than the computer can handle, or a non-16550 serial line is used. Overruns can also occur if too many high speed serial lines are active at one time for the processor's power.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Total number of async parity errors. These can be caused by a noisy transmission line.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Total number of bytes on this session, including all protocol overhead.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Total number of bytes after compression. This number compared with the TotalBytes value is the compression ratio.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Total number of compression dictionary flushes. When the data cannot be compressed, the compression dictionary is flushed so that newer data has a better chance of being compressed. One cause of data not compressing includes transferring compressed files over client drive mappings.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Total compression ratio of the server data stream.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Total number of errors of all types. Some example errors are lost acknowledgements (ACKs), badly formed packets, and so on.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Total number of time outs on the communication line from both the host and client sides of the connection. These are typically the result of a noisy line. On some high latency networks, this could be the result of the protocol time out being too short. Increasing the protocol time out on these types of lines improves performance by reducing needless re-transmissions.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Overall hit ratio for all protocol caches.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Total hits in all protocol caches. The protocol caches Windows objects that are likely to be re-used to avoid having to re-send them on the transmission line. Example objects are Windows icons and brushes. Hits in the cache represent objects that did not must be re-sent.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Total hits in all protocol caches. Total references to all protocol caches.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Total number of time outs on the communication line from both the host and client sides of the connection. These are typically the result of a noisy line. On some high latency networks, this could be the result of the protocol time out being too short. Increasing the protocol time out on these types of lines improves performance by reducing needless re-transmissions.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Total number of Terminal Services transport-level errors.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Number of times that a wait for an available send buffer was done by the protocols on both the server and client sides of the connection.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Total number of bytes on this session after all protocol overhead has been removed.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Total number of frames entered and produced before any additional protocol frames have been added.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Current size, in bytes, of the virtual address space the process is using. Use of virtual address space does not necessarily imply corresponding use of either disk or main memory pages. Virtual space is finite and, by using too much, the process can limit its ability to load libraries.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Maximum number of bytes of virtual address space the process has used at any one time. Use of virtual address space does not necessarily imply corresponding use of either disk or main memory pages. Maximum number of bytes of virtual address space the process has used at any one time. Use of virtual address space does not necessarily imply corresponding use of either disk or main memory pages. Virtual space is finite and, by using too much, the process might limit its ability to load libraries.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Current number of bytes in the working set of this process. 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 are then soft-faulted back longo the working set before they leave main memory.

Win32_PerfFormattedData_TermService_TerminalServicesSession: Maximum number of bytes in the working set of this process at any polong in time. 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 are then soft-faulted back longo the working set before they leave main memory.