Closed The3IC closed 1 month ago
Hi @The3IC,
Do you see that tiny little drop down carrot to the left of the 'V' in 'Video Decode'? If you click that, you should be able to select more options. What you want to select here is 'Compute'. Can you see if that shows some more activity?
Thanks, Ryan
And by the way -- the way that OpenVINO has been integrated into whisper.cpp is that only part of the whisper pipeline (the encoder, to be specific) is offloaded to OpenVINO -- the rest of the pipeline (the decode / token generation pieces) will still run on CPU. For larger whisper models, the encode portion of the pipeline is usually a small fraction of the overall pipeline -- so you'll still see CPU used quite heavily, and not so much GPU utilization.
These are the Intel GPU processors shown in Windows:
Only the "3D" shows in usage. I'm just comparing with for instance AI functions in Resolve which consistently work the GPUs at 90+%. Here is Resolve video render running:
Doing testing here around issue #187 also noticed that selecting the GPU (Intel on-chip) essentially seem to have no impact on the GPU load profile? On my particular computer CPU load hovers in the 30s while GPU is hardly loaded at all for GPU selection? For CPU selection, CPU loads are higher and GPU seems the same. Processing times with GPU are actually longer than with CPU?
CPU is i7-12700H, GPU is whatever is on that chip.
Typical load when GPU selected:
Typical load when CPU selected: