TABLE OF CONTENTS High-performance providers are implemented as instance providers. However, without going into the implementation details of High-performance providers, the major difference from standard instance providers is that they run as an in-process component of WMI or an application. (See Table 3.72.) The aim of a High-performance provider is to monitor data sent to the System Monitor of Windows 2000 or later. Having a High-performance provider has the advantage of not having WMI call the Performance Counter provider, which in turn, calls the performance library to collect the data. Basically, High-performance providers remove that layer, which greatly improves performance.
| Provider Name | Provider namespace | Class Provider | Instance Provider | Method Provider | Property Provider | Event Provider | Event Consumer Provider | Support Get | Support Put | Support Enumeration | Support Delete | Windows Server 2003 | Windows XP | Windows 2000 Server | Windows 2003 Professional | Windows NT 4.0 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| High Performance Providers | ||||||||||||||||
| HiperfCooker_v1 | Root/WMI | X | X | X | X | X | ||||||||||
| HiPerfCooker_v1 | Root/CIMV2 | X | X | X | X | X | ||||||||||
| NT5_GenericPerfProvider_V1 | Root/CIMV2 | X | X | X | X | X | X | X |
We must distinguish between two different High-performance providers in Windows:
The Performance Counter provider, which provides access to the raw counters data. This provider...
