Counters |
Definition |
Process(IxServer)\%Processor Time
|
The percentage of elapsed time that all IxServer threads used the processor to execute instructions. Code that was executed to handle some hardware interrupts and trap conditions is included in this count. |
Process(IxServer)\Working Set
|
The current size (in bytes) of the set of the memory pages touched recently by IxServer threads. 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. |
Process(IxServer)\Handle Count |
The total number of handles currently open by IxServer. This number is equal to the sum of the handles currently opened by each thread in IxServer. |
Process(IxServer)\Page File Byte
|
The current number of bytes that 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 the other files. Paging files are shared by all processes, and the lack of space in paging files can prevent other processes from allocation memory. |
Process(IxServer)\Pool Nonpaged Bytes |
The size in bytes of the nonpaged pool, an area of system memory (physical memory used by 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 this, so it might not equal Process\\Pool Nonpaged Bytes\\_Total. This counter shows the last observed value only, not an average. |
Process(IxServer)\Pool Paged Bytes
|
The size in bytes of 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 Pages Bytes is calculated differently than this, so it might not equal Process\\Pool Pages Bytes\\_Total. This counter shows the last observed value only, not an average. |
Process(IxServer)\Virtual Bytes |
The current size, in bytes, of the virtual address space that IxServer 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 the process can limit its ability to load libraries. |