Author jkloth
Recipients ammar2, giampaolo.rodola, jkloth, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2018-07-15.12:40:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1531658432.74.0.56676864532.issue34060@psf.upfronthosting.co.za>
In-reply-to
Content
Not that it matters all that much, but from a terminology standpoint, WMI != PDH != Performance Counters.

Performance counters (the objects, not the topic) are provided by DLLs registered in the HKLM\SYSTEM\CurrentControlSet\Services key.  Their data is accessed via registry API functions using the HKEY_PERFORMANCE_DATA root key.

PDH (Performance Data Helper) provides an abstraction layer that can access those values among other things like a GUI or writing to log files.

WMI (Windows Management Instrumentation) is yet another layer on top of PDH and raw Performance Counters.

In this case of the "System" performance counter object, it is provided by a performance DLL (perfos.dll in the case of Win10 1803).  If overhead (memory and/or CPU) is a concern, then accessing the counter data via the registry is the way to go.
History
Date User Action Args
2018-07-15 12:40:32jklothsetrecipients: + jkloth, paul.moore, vstinner, giampaolo.rodola, tim.golden, zach.ware, steve.dower, ammar2
2018-07-15 12:40:32jklothsetmessageid: <1531658432.74.0.56676864532.issue34060@psf.upfronthosting.co.za>
2018-07-15 12:40:32jklothlinkissue34060 messages
2018-07-15 12:40:32jklothcreate