I've just had an interesting conversation with a new user over at BOINC Dev. He was confused because he thought his GPU wasn't working properly.

Turns out that Windows 10 now has (from a recent update, we think) a GPU usage meter in Task Manager. But it can't see GPUGrid - and possibly general CUDA - activity. Here's one of mine:



Just a heads-up in case anyone else gets confused - it's Microsoft, not you.

Turns out that Windows 10 now has (from a recent update, we think) a GPU usage meter in Task Manager.

This feature was rolled out to the genral public in the so called "creators fall update" (v1709).
Earlier versions do not have this feature in Task Manager.

But it can't see GPUGrid - and possibly general CUDA - activity.

True. It can't see Einstein@home OpenCL tasks too. It can only see the GPU memory usage.
If I recall it correctly it can see the iGPU usage though.
The other shortcoming of Task Manager is that it does not recognize DDR4 memory type (and some DDR3 memory type too), so it displays only the size of memory (or shows "other" as its type).

Just a heads-up in case anyone else gets confused - it's Microsoft, not you.

Slightly connected to this issue that Microsoft is working on a solution to eliminate the WDDM overhead of GPGPU applications by allowing GPGPU APIs to directly run kernels (that would make GPUGrid tasks 5-10-15% faster on Windows 7-10).

The new GPU item(s) in Task Manager, lists usages for each "engine" that the GPU supports.

For my GTX 980 Ti GPUs, when I select one of them in Task Manager, there are 12 engines of activity to choose from. The CUDA compute activity actually DOES show up whenever I select the "Compute_0" engine for each GPU.

I'm not sure how the "Overall usage" value gets calculated for the left pane, but I suspect it excludes compute intentionally, in order to show that the GPU is otherwise available for non-compute-use.

Regards,
Jacob

Here is a link to some Windows 10 Feedback that I just submitted.
If you want Microsoft to change this, then please click the link and then click Upvote.

https://aka.ms/Cpvo3x

Thanks,
Jacob

Thanks for that. compute_0 shows SETI OpenCL usage too, so that would be the one to go for.

Unfortunately, on my machine, Task Manager:

Does NOT remember that I last viewed the performance tab.
DOES remember that I viewed the performance of the GPU.
Does NOT remember that I want to view compute_0.

That's just sloppy GUI design. I'll check your report and see if you've covered that.

Link not visible from the Windows 7 machine in the warm room. I'll have to go back upstairs into the cold. Later.

Feedback needs to be submitted as one request per feedback item.
I submitted the "Include Compute_0 in main GPU usage" item, which I linked to.
If you want to submit additional feedback items, feel free.

Feedback hub doesn't let me have access to your report to upvote it, but has let me make my own (anonymous) report on the consistency issue.

Hm, that's strange. I wonder if it's because I submitted it using an Insider account, or maybe because I submitted it using an Insider build.
If you're sure you can't see my feedback, then feel free to submit your own version. Microsoft can put them into "collections" later.
Sloppy all around, for Microsoft.

Windows 10 is a horror and will hang on to Windows 7 until 2020 but they're messing with that as well. Video driver update yesterday as important update selected by default.

Microsoft is really becoming oppressive.

Okay ...
Let's try to stick to the topic of this thread - Windows 10 Task Manager, and submitting feedback to get some things changed..

The new GPU item(s) in Task Manager, lists usages for each "engine" that the GPU supports.

For my GTX 980 Ti GPUs, when I select one of them in Task Manager, there are 12 engines of activity to choose from. The CUDA compute activity actually DOES show up whenever I select the "Compute_0" engine for each GPU.

Thanks for that!

I'm not sure how the "Overall usage" value gets calculated for the left pane, but I suspect it excludes compute intentionally, in order to show that the GPU is otherwise available for non-compute-use.

Here is a link to some Windows 10 Feedback that I just submitted.
If you want Microsoft to change this, then please click the link and then click Upvote.

https://aka.ms/Cpvo3x


Regards,
Jacob

I've upvoted your feedback.

It got my upvote and a comment as well.

Is that "Compute_0" similar to the P-states of GPUs? 3D clocks for gaming is a different P-state than compute. For NV its P2 in Windows and Linux for compute (BOINC and FAH).

To my knowledge...

A P-State is a performance state. P0 is maximum 3D performance, and I think P2 might be 2D standard mode. See here: http://docs.nvidia.com/gameworks/content/gameworkslibrary/coresdk/nvapi/group__gpupstate.html

"Compute_0", as shown in Windows 10 Task Manager using v1709 Fall Creators Update ... is an engine of the GPU. Think of it more as a "method of utilization", rather than a state.

As another example:
- Run a CUDA/OpenCL application
- Install Process Explorer
- Click View > System Information > GPU
- Click "Engines" button at the bottom

You'll see there, too, the "engines" where usage can be detected, for your GPU(s). I have 2 GTX 980 Ti GPUs, and 40 engines on that screen, with 2 of them highly active when GPUGrid is running. Just like Task Manager, those 2 are definitely my "Compute_0" engines on each GPU :)

Regards,
Jacob