On hybrid laptop, satty is using the dGPU

[fboulay]

Version

0.20.1

Description

Satty is using my Nvidia dGPU on my hybrid laptop.
The rest of the system (Arch) is running on the iGPU. I expect Satty to have the same behavior.

The workaround I have found to avoid this issue is starting satty with the command VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/intel_icd.x86_64.json satty ...

[RobertMueller2]

Satty doesn't do anything to prefer one GPU over the other, so I doubt we can do anything from Satty perspective to fix this.

It's worth noting though that rendering is done with femtovg, which utilises OpenGL. I'd expect that this follows the same configuration as e.g. glxgears.

[RobertMueller2]

FWIW, on my laptop (NVidia dGPU, AMD iGPU), Satty is using iGPU. Unless I run satty with DRI_PRIME=1 (and some other nvidia related vars), then it uses the dGPU. So I suggest to try different settings for DRI_PRIME.

[fboulay]

The variable DRI_PRIME is for OpenGL, I think the app is using Vulkan. Using DRI_PRIME with various values does not change anything.

For your information, this issue is specific to this Rust app. Other Rust apps do not have this behavior.

[RobertMueller2]

Again, Satty does not do anything to retrieve a GPU list or even configure one.

[fboulay]

Yes I understand. I will continue my research on this topic.

[RobertMueller2]

If you find anything, let us know. I'll also try to look more closely during the next time.

My general feeling is that this is a deeper layer we're currently not touching or ever going to touch, but depending on what we find out we can always add it to readme, future documentation, Wiki FAQ, etc.

[gabm]

It is likely related to femtovg.. they use HW acceleration with OpenGL iirc