[Feature] Support multiple GPU

[balciseri]

What problem does this solve?

I can't track my NVIDIA GPU because i can only see the INTEGRATED AMD GPU of the processor.

Thanks you.

Proposed solution

Possibility to select primary or secondary GPU

Alternatives considered

No response

How blocking is this for you?

Nice to have

[erez-c137]

Thanks @balciseri — and sorry for the wait. You filed this as a "nice to have" feature request, and I went looking for where the picker would go and instead found a bug. 🙃

NetSpeedTray builds its GPU counter list once, at startup, and it's a list of per-process counters. So it only ever sees processes that already existed when it launched — desktop and system stuff, which Windows runs on your integrated AMD. Every app you start afterwards, including whatever Windows routes to the NVIDIA, gets a new process ID we never subscribed to. The number simply never grows to include it.

On a single-GPU machine this is invisible, because the compositor roughly tracks total load — which is why it's gone unnoticed since v1.3.1.

Two things you can do right now to confirm it:

1. Start your NVIDIA workload, then open the Monitor window → Hardware tab. That list uses a different, correct query. If your app shows a high GPU% there while the widget shows something low, that's this bug confirmed — no new build needed.

2. Workaround: with the workload already running, open Settings and hit Save. That forces a rebuild of the counter list, and it should start picking up the NVIDIA.

I'm fixing the counter query in the next patch.

Being honest about what that does and doesn't get you, though: the widget shows the highest load across your adapters, so once fixed it will correctly show the NVIDIA when it's busy — but at idle it'll still show the iGPU, because that's the one driving your desktop. The actual "pick which GPU to monitor" selector you asked for is a bigger job — it needs adapter enumeration, a settings control, and translations into 13 languages — so I'm keeping this issue open for that and lining it up behind the current release. No date from me; spare-time project. 🙏

Thanks for reporting it — you turned up something broader than you were asking about.

[erez-c137]

The counter fix is merged (#239) and will be in 2.1.3, @balciseri.

To be precise about what that does for you: the widget now rebuilds its GPU counter list on every sample instead of once at startup, so your NVIDIA is measured whenever it's actually doing something. At idle you'll still see the integrated AMD, because that's the one driving your desktop and we show the highest load across adapters.

Keeping this open for the actual "pick which GPU to monitor" selector you asked for — that still needs adapter enumeration, a settings control and translations across 13 languages, so it's lined up behind the current release rather than in it.

If you'd like to sanity-check the fix when 2.1.3 ships: start your NVIDIA workload and compare the widget against the Monitor window's Hardware tab. They should agree now. Before this they wouldn't have. 🙏

[erez-c137]

v2.1.3 is out with the counter fix in it, @balciseri.

To be precise about what changed for you: the widget now rebuilds its GPU counter list on every sample instead of once at startup, so your NVIDIA is measured whenever it is actually doing something. At idle you will still see the integrated AMD, because that is the card driving your desktop and we report the highest load across adapters.

One thing I would value if you have a minute: open the Monitor → Hardware tab while something is genuinely using the NVIDIA, and tell me whether the GPU number there agrees with the widget on the taskbar. That is the check that tells me the fix behaves the same on a real hybrid laptop as it does here.

Keeping this open for what you actually asked for - the ability to pick which GPU is shown. That is still a real feature request and it is on the list; you just happened to find a bug on the way to it. Thank you for filing it as a "nice to have" and being right that something was off. 💙

[balciseri]

Two things you can do right now to confirm it:

1. Start your NVIDIA workload, then open the Monitor window → Hardware tab. That list uses a different, correct query. If your app shows a high GPU% there while the widget shows something low, that's this bug confirmed — no new build needed.

True, i see the 94% GPU utilization

2. Workaround: with the workload already running, open Settings and hit Save. That forces a rebuild of the counter list, and it should start picking up the NVIDIA.

Yes as you said.

[balciseri]

Ok i have updated to v2.1.3

One thing I would value if you have a minute: open the Monitor → Hardware tab while something is genuinely using the NVIDIA, and tell me whether the GPU number there agrees with the widget on the taskbar. That is the check that tells me the fix behaves the same on a real hybrid laptop as it does here

Yes, they do agree now!

Thank you!

[erez-c137]

That is exactly what I needed to hear - thank you for testing it so quickly, @balciseri. 🙏

A hybrid laptop is the one configuration I cannot check here, so "they do agree now" from an actual dual-GPU machine is worth more than any test I can write. The counter fix is confirmed working in the wild.

Keeping this open for the original request - being able to pick which GPU is displayed, rather than always seeing the highest load across adapters. That is a real feature and it stays on the list; you just happened to surface a bug on the way to it, and finding it changed the release.