Windows 2000 Terminal Services Session Statistics
The following table describes the Windows 2000 Terminal Services Sessions Statistics metric group.
Metric group: Windows 2000 Terminal Services Session Statistics
Metric and available units |
Description |
---|---|
Services Session Name |
The name of a terminal service session. |
% Processor Time |
Is the 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. On multi-processor machines the maximum value of the counter is 100% times the number of processors. |
% User Time |
Is the percentage of elapsed time that this process' 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 Windows NT Executive, Kernel, and device drivers. Unlike some early operating systems, Windows NT 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 Windows NT on behalf of your application might appear in other subsystem processes in addition to the privileged time in your process. |
% Privileged Time |
Is the percentage of elapsed time that the threads of the process have spent executing code in privileged mode. When a Windows NT system service is called, the service will often run 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. Unlike some early operating systems, Windows NT 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 Windows NT on behalf of your application might appear in other subsystem processes in addition to the privileged time in your process. |
Virtual Bytes Peak |
Virtual Bytes Peak is the 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 however finite, and by using too much, the process might limit its ability to load libraries. |
Virtual Bytes |
Virtual Bytes is the 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. |
Page Faults |
Page Faults/sec is the rate 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 will 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 Peak |
Working Set Peak is the maximum number of bytes in the Working Set of this process at any point 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 will then be soft-faulted back into the Working Set before they leave main memory. |
Working Set |
Working Set is the 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 will then be soft-faulted back into the Working Set before they leave main memory. |
Page File Bytes Peak |
Page File Bytes Peak is the 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. |
Page File Bytes |
Page File Bytes is the 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. |
Private Bytes |
Private Bytes is the current number of bytes this process has allocated that cannot be shared with other processes. |
Thread Count |
The 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. |
Pool Paged Bytes |
Pool Paged Bytes is the 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. Memory: Pool Paged Bytes is calculated differently than Process: Pool Paged Bytes, so it might not equal Process: Pool Paged Bytes: _Total. This counter displays the last observed value only; it is not an average. |
Pool Nonpaged Bytes |
Pool Nonpaged Bytes is the 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. Memory: Pool Nonpaged Bytes is calculated differently than Process: Pool Nonpaged Bytes, so it might not equal Process: Pool Nonpaged Bytes: _Total. This counter displays the last observed value only; it is not an average. |
Handle Count |
The total number of handles currently open by this process. This number is the sum of the handles currently open by each thread in this process. |
Input WdBytes |
Number of bytes input on this session after all protocol overhead has been removed. |
Input WdFrames |
The number of frames input after any additional protocol added frames have been removed. |
Input WaitForOutBuf |
The number of times that a wait for an available send buffer was done by the protocols on the client side of the connection. |
Input Frames |
Number of frames (packets) input on this Session. |
Input Bytes |
Number of bytes input on this session that includes all protocol overhead. |
Input Compressed Bytes |
Number of bytes input after compression. This number compared with the Total Bytes input is the compression ratio. |
Input Compress Flushes |
Number of input compression dictionary flushes. When the data can not be compressed, the compression dictionary is flushed so that newer data has a better chance of being compressed. Some causes of data not compressing includes transferring compressed files over Client Drive Mapping. |
Input Errors |
Number of input errors of all types. Some example input errors are lost ACK's, badly formed packets, and so on. |
Input Timeouts |
The total number of timeouts 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 timeout being too short. Increasing the protocol timeout on these types of lines will improve performance by reducing needless re-transmissions. |
Input Async Frame Error |
Number of input async framing errors. These can be caused by a noisy transmission line. Using a smaller packet size might help in some cases. |
Input Async Overrun |
Number of input 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. |
Input Async Overflow |
Number of input async overflow errors. These can be caused by a lack of buffer space available on the host. |
Input Async Parity Error |
Number of input async parity errors. These can be caused by a noisy transmission line |
Input Transport Errors |
Number of Terminal Services transport-level errors on input. |
Output WdBytes |
Number of bytes output on this session after all protocol overhead has been removed. |
Output WdFrames |
The number of frames output before any additional protocol frames have been added. |
Output WaitForOutBuf |
This is the number of times that a wait for an available send buffer was done by the protocol on the server side of the connection. |
Output Frames |
Number of frames (packets) output on this session. |
Output Bytes |
Number of bytes output on this Session that includes all protocol overhead. |
Output Compressed Bytes |
Number of bytes output after compression. This number compared with the Total Bytes output is the compression ratio. |
Output Compress Flushes |
Number of output compression dictionary flushes. When the data can not be compressed, the compression dictionary is flushed so that newer data has a better chance of being compressed. Some causes of data not compressing includes transferring compressed files over Client Drive Mapping. |
Output Errors |
Number of output errors of all types. Some example output errors are lost ACK's, badly formed packets, and so on. |
Output Timeouts |
The total number of timeouts 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 timeout being too short. Increasing the protocol timeout on these types of lines will improve performance by reducing needless re-transmissions. |
Output Async Frame Error |
Number of output async framing errors. This could be caused by a hardware or line problem. |
Output Async Overrun |
Number of output async overrun errors. |
Output Async Overflow |
Number of output async overflow errors. |
Output Async Parity Error |
Number of output async parity errors. These can be caused by a hardware or line problem. |
Output Transport Errors |
Number of Terminal Services transport-level errors on output. |
Total WdBytes |
Total number of bytes on this Session after all protocol overhead has been removed. |
Total WdFrames |
The total number of frames input and output before any additional protocol frames have been added. |
Total WaitForOutBuf |
The 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. |
Total Frames |
Total number of frames (packets) on this Session. |
Total Bytes |
Total number of bytes on this Session that includes all protocol overhead. |
Total Compressed Bytes |
Total number of bytes after compression. This number compared with the total bytes is the compression ratio. |
Total Compress Flushes |
Total number of compression dictionary flushes. When the data can not be compressed, the compression dictionary is flushed so that newer data has a better chance of being compressed. Some causes of data not compressing includes transferring compressed files over Client Drive Mapping. |
Total Errors |
Total number of errors of all types. Some example errors are lost ACK's, badly formed packets, and so on. |
Total Timeouts |
The total number of timeouts 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 timeout being too short. Increasing the protocol timeout on these types of lines will improve performance by reducing needless re-transmissions. |
Total Async Frame Error |
Total number of async framing errors. These can be caused by a noisy transmission line. Using a smaller packet size might help in some cases. |
Total Async Overrun |
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. |
Total Async Overflow |
Total number of async overflow errors. These can be caused by a lack of buffer space available on the host. |
Total Async Parity Error |
Total number of async parity errors. These can be caused by a noisy transmission line. |
Total Transport Errors |
Total number of Terminal Services transport-level errors. |
Total Protocol Cache Reads |
Total references to all protocol caches. |
Total Protocol Cache Hits |
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 need to be re-sent. |
Total Protocol Cache Hit Ratio |
Overall hit ratio for all protocol caches. |
Protocol Bitmap Cache Reads |
Number of references to the protocol bitmap cache. |
Protocol Bitmap Cache Hits |
Number of hits in the protocol bitmap cache. |
Protocol Bitmap Cache Hit Ratio |
Hit ratio in the protocol bitmap cache. A higher hit ratio means better performance since 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. |
Protocol Glyph Cache Reads |
Number of references to the protocol glyph cache. |
Protocol Glyph Cache Hits |
Number of hits in the protocol glyph cache. |
Protocol Glyph Cache Hit Ratio |
Hit ratio in the protocol glyph cache. A higher hit ratio means better performance since 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. |
Protocol Brush Cache Reads |
Number of references to the protocol brush cache. |
Protocol Brush Cache Hits |
Number of hits in the protocol brush cache. |
Protocol Brush Cache Hit Ratio |
Hit ratio in the protocol brush cache. A higher hit ratio means better performance since 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. |
Protocol Save Screen Bitmap Cache Reads |
Number of references to the protocol save screen bitmap cache. |
Protocol Save Screen Bitmap Cache Hits |
Number of hits in the protocol save screen bitmap cache. |
Protocol Save Screen Bitmap Cache Hit Ratio |
Hit ratio in the protocol save screen bitmap cache. A higher hit ratio means better performance since 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. |
Input Compression Ratio |
Compression ratio of the server input data stream. |
Output Compression Ratio |
Compression ratio of the server output data stream. |
Total Compression Ratio |
Total compression ratio of the server data stream. |
Comments
Log in or register to comment.