Oh cool! Win10 GPU monitoring

[Diggs]

Available with the Creators Update this fall -

Full article here -
https://www.extremetech.com/computi...Extremetech)&utm_content=FeedBurner+user+view

 

[Archon Prime]

Interesting.

 

[nlinecomputers]

'bout time.

 

[NYJimbo]

But don't they have to know how to talk to and read each type of GPU ? Other programs have been working on this for years and every year they have to add new GPU makes/types to their database before they can properly be probed and reported on.

So, if I understand this, they are just NOW getting into this and will not likely have as much GPU detection/probe/analysis as other programs ?

 

[Blues]

@NYJimbo IIRC many GPUs have drivers certified by Windows this should give them a leg up to accurately ID and communicate with the GPU.

 

[Mike_IRE]

Interesting , i wonder will they add it to Server OS.

 

[phaZed]

But don't they have to know how to talk to and read each type of GPU ? Other programs have been working on this for years and every year they have to add new GPU makes/types to their database before they can properly be probed and reported on.

Well, yes and no. The video card reports *some* of its operating properties on the SM bus that is easily queried. WMI has supported this method since Vista, so in theory, MS could have included GPU support in Task Manager long ago. MS is likely using this method which is why it is limited in Task Manager. I believe they are using this method for the added benefit of not needing to query or rely on a driver to do so.

If they want to query the video driver instead, which offers much more info and usually in realtime, that's easy too... considering everyone publishes how their driver works and how to query it. It simply queries the VBIOS registers directly.

For NVIDIA, a programmer would use the NVIDIA Management Library (NVML) which is fully documented. A use of NVML on linux, for instance, would output something like this from nvidia-smi.

Long story short, there is no reason 'other programs' couldn't read the values correctly as soon as a driver for said card is available (Usually before launch)!