The trick we use at work is to take note of the instantenous power consumed. The more it's consuming the more compute it is doing. As far as macro indicators, I'm not sure you can do better than that, without profiling.
This feels like the answer to a problem I’ve had all week.
I’ve been using PixiJS (WebGL) for an project and Chrome profiler says the GPU is in use almost 100% of every frame. And nvtop says the GPU is 35% utilized by that (well isolated) chrome tab. But it’s a single quad being rendered at 60fps on an RTX 4060, so that’s obviously misleading… I hope.
The trick we use at work is to take note of the instantenous power consumed. The more it's consuming the more compute it is doing. As far as macro indicators, I'm not sure you can do better than that, without profiling.
This feels like the answer to a problem I’ve had all week.
I’ve been using PixiJS (WebGL) for an project and Chrome profiler says the GPU is in use almost 100% of every frame. And nvtop says the GPU is 35% utilized by that (well isolated) chrome tab. But it’s a single quad being rendered at 60fps on an RTX 4060, so that’s obviously misleading… I hope.