IProcessPerfDataInfo Properties |
The IProcessPerfDataInfo type exposes the following members.
Name | Description | |
---|---|---|
Description |
Gets or sets the description.
(Inherited from IProcessInfoBase.) | |
ElapsedTime |
Gets or sets the elapsed time.
(Inherited from IProcessInfoBase.) | |
HandleCount |
Win32_PerfFormattedData_PerfProc_Process: Total number of handles that the process has open.
This number is the sum of the handles currently opened by each thread in the process.
| |
IDProcess |
Gets or sets the ID process.
(Inherited from IProcessInfoBase.) | |
IODataBytesPerSec |
Win32_PerfFormattedData_PerfProc_Process: Rate at which the process is reading and writing
bytes in I/O operations. This property counts all I/O activity generated by the process,
including file, network, and device I/O operations.
| |
IODataOperationsPerSec |
Win32_PerfFormattedData_PerfProc_Process: Rate at which the process is issuing read and
write I/O operations. This property counts all I/O activity generated by the process,
including file, network, and device I/O operations.
| |
IOOtherBytesPerSec |
Win32_PerfFormattedData_PerfProc_Process: Rate at which the process is issuing bytes to
I/O operations that do not involve data such as control operations. This property counts
all I/O activity generated by the process, including file, network, and device I/O
operations.
| |
IOOtherOperationsPerSec |
Win32_PerfFormattedData_PerfProc_Process: Rate at which the process is issuing I/O
operations that are neither read nor write operations. An example of this type of operation
would be a control function. This property counts all I/O activity generated by the process,
including file, network, and device I/O operations.
| |
IOReadBytesPerSec |
Win32_PerfFormattedData_PerfProc_Process: Rate at which the process is reading bytes from
I/O operations. This property counts all I/O activity generated by the process, including
file, network, and device I/O operations.
| |
IOReadOperationsPerSec |
Win32_PerfFormattedData_PerfProc_Process: Rate at which the process is issuing read I/O
operations. This property counts all I/O activity generated by the process, including file,
network, and device I/O operations.
| |
IOWriteBytesPerSec |
Win32_PerfFormattedData_PerfProc_Process: Rate at which the process is writing bytes to
I/O operations. This property counts all I/O activity generated by the process, including
file, network, and device I/O operations.
| |
IOWriteOperationsPerSec |
Win32_PerfFormattedData_PerfProc_Process: Rate at which the process is issuing write I/O
operations. This property counts all I/O activity generated by the process, including file,
network, and device I/O operations.
| |
Name |
Gets or sets the name.
(Inherited from IProcessInfoBase.) | |
PageFaultsPerSec |
Win32_PerfFormattedData_PerfProc_Process: Rate of page faults by 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.
| |
PageFileBytes |
Win32_PerfFormattedData_PerfProc_Process: Value, in bytes, that this process has used in
the paging file(s). Paging files 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.
| |
PageFileBytesPeak |
Win32_PerfFormattedData_PerfProc_Process: Maximum number, in 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 other files. Paging files are shared by all processes,
and lack of space in paging files can prevent other processes from allocating memory.
| |
PercentPrivilegedTime |
Percentage of elapsed time that this thread has spent executing code in privileged
mode. When the operating system 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 and interrupts. Unlike some early operating systems, 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.
(Inherited from IProcessInfoBase.) | |
PercentProcessorTime |
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 is included in this count.
(Inherited from IProcessInfoBase.) | |
PercentUserTime |
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.
(Inherited from IProcessInfoBase.) | |
PoolNonpagedBytes |
Win32_PerfFormattedData_PerfProc_Process: Value, in 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. The
PoolNonpagedBytes in Win32_PerfFormattedData_PerfOS_Memory is calculated differently than
the PoolPagedBytes property in Win32_PerfFormattedData_PerfProc_Process, so it might not
equal the total of PoolPagedBytes for all instances of Win32_PerfFormattedData_PerfProc_Process.
This property displays the last observed value only; it is not an average.
| |
PoolPagedBytes |
Win32_PerfFormattedData_PerfProc_Process: Value, in 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. The PoolNonpagedBytes property in
Win32_PerfFormattedData_PerfOS_Memory is calculated differently than the PoolPagedBytes
property in Win32_PerfFormattedData_PerfProc_Process, so it might not equal the total of
PoolPagedBytes for all instances of Win32_PerfFormattedData_PerfProc_Process. This property
displays the last observed value only; it is not an average.
| |
PriorityBase |
Gets or sets the priority base.
(Inherited from IProcessInfoBase.) | |
PrivateBytes |
Win32_PerfFormattedData_PerfProc_Process: Current value, in bytes, that this process has
allocated that cannot be shared with other processes.
| |
ThreadCount |
Win32_PerfFormattedData_PerfProc_Process: 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.
| |
TimestampObject |
Object-defined timestamp, defined by the provider.
(Inherited from IProcessInfoBase.) | |
TimestampSys100Ns |
Win32_PerfRawData_PerfProc_Process: Timestamp_Sys100NS:
Timestamp value in 100 nanosecond units.
(Inherited from IProcessInfoBase.) | |
VirtualBytes |
Win32_PerfFormattedData_PerfProc_Process: Current size, in bytes, of the virtual address
space that 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.
| |
VirtualBytesPeak |
Win32_PerfFormattedData_PerfProc_Process: Maximum number, in bytes, of virtual address
space that 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.
| |
WorkingSet |
Win32_PerfFormattedData_PerfProc_Process: Maximum number, in 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 required, they
are then soft-faulted back into the working set before they leave main memory.
| |
WorkingSetPeak |
Win32_PerfFormattedData_PerfProc_Process: Maximum number, in bytes, in the working set of
this process at any point. 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 required, they are
then soft-faulted back into the working set before they leave main memory.
| |
WorkingSetPrivate |
Specific Working Set memory that cannot be shared with other processes.
|