Represents a Windows NT performance counter component.
Assembly: System (in System.dll)
Initializes a new, read-only instance of theclass, without associating the instance with any system or custom performance counter.
Initializes a new, read-only instance of theclass and associates it with the specified system or custom performance counter on the local computer. This constructor requires that the category have a single instance.
|PerformanceCounter(String, String, Boolean)|
Initializes a new, read-only or read/write instance of theclass and associates it with the specified system or custom performance counter on the local computer. This constructor requires that the category contain a single instance.
|PerformanceCounter(String, String, String)|
Initializes a new, read-only instance of theclass and associates it with the specified system or custom performance counter and category instance on the local computer.
|PerformanceCounter(String, String, String, Boolean)|
Initializes a new, read-only or read/write instance of theclass and associates it with the specified system or custom performance counter and category instance on the local computer.
|PerformanceCounter(String, String, String, String)|
Initializes a new, read-only instance of theclass and associates it with the specified system or custom performance counter and category instance, on the specified computer.
Gets or sets the name of the performance counter category for this performance counter.
Gets the description for this performance counter.
Gets or sets the name of the performance counter that is associated with thisinstance.
Gets the counter type of the associated performance counter.
Gets or sets the lifetime of a process.
Gets or sets an instance name for this performance counter.
Gets or sets the computer name for this performance counter
Gets or sets the raw, or uncalculated, value of this counter.
Gets or sets a value indicating whether thisinstance is in read-only mode.
Begins the initialization of ainstance used on a form or by another component. The initialization occurs at runtime.
Closes the performance counter and frees all the resources allocated by this performance counter instance.
Frees the performance counter library shared state allocated by the counters.
Creates an object that contains all the relevant information required to generate a proxy used to communicate with a remote object.(Inherited from MarshalByRefObject.)
Decrements the associated performance counter by one through an efficient atomic operation.
Ends the initialization of ainstance that is used on a form or by another component. The initialization occurs at runtime.
Determines whether the specified object is equal to the current object.(Inherited from Object.)
Serves as the default hash function. (Inherited from Object.)
Retrieves the current lifetime service object that controls the lifetime policy for this instance.(Inherited from MarshalByRefObject.)
Increments the associated performance counter by one through an efficient atomic operation.
Increments or decrements the value of the associated performance counter by a specified amount through an efficient atomic operation.
Obtains a lifetime service object to control the lifetime policy for this instance.(Inherited from MarshalByRefObject.)
Obtains a counter sample, and returns the raw, or uncalculated, value for it.
Obtains a counter sample and returns the calculated value for it.
Deletes the category instance specified by the InstanceName property.object
Obsolete.Specifies the size, in bytes, of the global memory shared by performance counters. The default size is 524,288 bytes.
Thecomponent can be used for both reading existing predefined or custom counters and publishing (writing) performance data to custom counters.
There are numerous predefined counters listed in the Windows Performance Monitor's Add Counters dialog box. To learn about the .NET Framework performance counters, see Performance Counters in the .NET Framework.
This type implements the IDisposable interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its Dispose method in a try/catch block. To dispose of it indirectly, use a language construct such as using (in C#) or Using (in Visual Basic). For more information, see the “Using an Object that Implements IDisposable” section in the IDisposable interface topic.
In versions 1.0 and 1.1 of the .NET Framework, this class requires immediate callers to be fully trusted. Starting with the .NET Framework version 2.0, this class requires PerformanceCounterPermission for specific actions. It is strongly recommended that PerformanceCounterPermission not be granted to semi-trusted code. The ability to read and write performance counters allows code to perform actions such as enumerating executing processes and obtaining information about them.
In addition, passing a PerformanceCounterCategory or , to less trusted code.object to less-trusted code can create a security issue. Never pass performance counter objects, such as a
To read from a performance counter, create an instance of the CategoryName, CounterName, and, optionally, the InstanceName or MachineName properties, and then call the NextValue method to take a performance counter reading.class, set the
To publish performance counter data, create one or more custom counters using the PerformanceCounterCategory.Create method, create an instance of the class, set the CategoryName, CounterName and, optionally, InstanceName or MachineName properties, and then call the IncrementBy, Increment, or Decrement methods, or set the RawValue property to change the value of your custom counter.
The Increment, IncrementBy, and Decrement methods use interlocks to update the counter value. This helps keep the counter value accurate in multithreaded or multiprocess scenarios, but also results in a performance penalty. If you do not need the accuracy that interlocked operations provide, you can update the RawValue property directly for up to a 5 times performance improvement. However, in multithreaded scenarios, some updates to the counter value might be ignored, resulting in inaccurate data.
The counter is the mechanism by which performance data is collected. The registry stores the names of all the counters, each of which is related to a specific area of system functionality. Examples include a processor's busy time, memory usage, or the number of bytes received over a network connection.
Each counter is uniquely identified through its name and its location. In the same way that a file path includes a drive, a directory, one or more subdirectories, and a file name, counter information consists of four elements: the computer, the category, the category instance, and the counter name.
The counter information must include the category, or performance object, that the counter measures data for. A computer's categories include physical components, such as processors, disks, and memory. There are also system categories, such as processes and threads. Each category is related to a functional element within the computer and has a set of standard counters assigned to it. These objects are listed in the Performance object drop-down list of the Add Counters dialog box within the Windows 2000 System Monitor, and you must include them in the counter path. Performance data is grouped by the category to which is it related.
In certain cases, several copies of the same category can exist. For example, several processes and threads run simultaneously, and some computers contain more than one processor. The category copies are called category instances, and each instance has a set of standard counters assigned to it. If a category can have more than one instance, an instance specification must be included in the counter information.
To obtain performance data for counters that required an initial or previous value for performing the necessary calculation, call the NextValue method twice and use the information returned as your application requires.
Performance counter categories installed with the .NET Framework 2.0 use separate shared memory, with each performance counter category having its own memory. You can specify the size of separate shared memory by creating a DWORD named FileMappingSize in the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<category name>\Performance. The FileMappingSize value is set to the shared memory size of the category. The default size is 131072 decimal. If the FileMappingSize value is not present, the fileMappingSize attribute value for the performanceCounters element specified in the Machine.config file is used, causing additional overhead for configuration file processing. You can realize a performance improvement for application startup by setting the file mapping size in the registry. For more information about the file mapping size, see <performanceCounters> Element.
Performance counters are not supported on Windows 98 or Windows Millennium Edition (Me).
The following code example demonstrates the use of the AverageCount64 counter type. The example creates categories, sets up counters, collects data from the counters, and calls the CounterSampleCalculator class to interpret the performance counter data. The intermediate and final results are displayed in the console window. For additional examples of other performance counter types, see the PerformanceCounterType enumeration.class to create and use an
Available since 1.1
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.