Supporting the Win32_PerfFormattedData Class

When writing a high-performance provider that derives classes from Win32_PerfFormattedData, you must follow specific conventions so that WMI can calculate the property values.

Note

Writing a WMI high-performance provider to create performance counters is not recommended on any version of the Windows operating system. For more information, see Making an Instance Provider into a High-Performance Providerand Performance Libraries and WMI.

 

The following procedure describes how to support the Win32_PerfFormattedData class.

To support the Win32_PerfFormattedData class

1. Create your class in the same namespace as the corresponding raw class. The class must be derived from Win32_PerfFormattedData and have the HiPerf qualifier set to TRUE. For more information about creating your own class for WMI, see Designing Managed Object Format (MOF) Classes.

2. Specify "HiPerfCooker_v1" in the Provider qualifier.

3. Specify the following class-level qualifiers in addition to the qualifiers used for the raw classes:

   • AutoCook
   • Autocook_RawClass
   • Cooked
   • Costly
   • Dynamic
   • HiPerf
   • Locale
   • PerfDefault
   • Provider
   • Singleton

   Note

   Do not set any value for GenericPerfCtr, PerfIndex, or HelpIndex because these will be set by the ADAP process. For more information, see Class Qualifiers for Performance Counter Classes.

    

4. Include a key property called Name in your class (this property is not required for singleton classes).

   The value of the Name property must be the same as the corresponding raw class. You must not use any key property other than Name on your class.

5. Create properties data typed as either DWORD (uint32) or QWORD (uint64).

   The properties must correspond either to a property in the raw class or a property in the class you are creating.

6. Specify the following property level qualifiers for all properties in your class in addition to the PerfIndex and PerfDetail qualifiers used for the raw class properties:

   • Base
   • CookingType
   • Counter
   • PerfTimeStamp
   • PerfTimeFreq
   • SampleWindow

   For more information, see Property Qualifiers for Performance Counter Classes. In addition, the Winperf.h header file contains values that you can specify for PerfDetail and CounterType.

7. Make sure your provider meets the performance requirements.

Performance Requirements

When you write a high-performance provider, its performance must meet the following requirements:

• Opening the high-performance DLL file can take no more than 100 milliseconds. Overall, opening each the high-performance provider and performance library cannot exceed 5 seconds.
• Data refresh can take no more than 10 milliseconds per collect. On an overall refresh and collect operation, all the high-performance providers together cannot take more than 800 milliseconds.
• The overall CPU load for all high-performance providers cannot exceed 6-7% CPU overhead interactively or 5% for logging.

Related topics

Making an Instance Provider into a High-Performance Provider