Dedicated GPU not being used, sluggish performance

Tagged: performance, webgl

This topic has 7 replies, 2 voices, and was last updated 2 years, 5 months ago by Alexander Kovelenov.

Viewing 8 posts - 1 through 8 (of 8 total)

Author

Posts
2021-11-12 at 2:31 pm #46924

Yorick
Customer

Hi,

I have a dedicated GPU, but even when Verge3D really stresses my integrated GPU (UHD 630), it doesn’t switch to my dedicated GPU (GeForce GTX 1050 Ti) – Windows 10, latest chrome build.

Colleagues on IOS suffer from the same issue. It really makes the whole browser lag, but never switches to the dedicated GPU.

When we force the browser in dedicated gpu mode, then it runs smooth.

This makes our model almost unusable… Any help would be greatly appreciated!

2021-11-12 at 5:19 pm #46929

Alexander Kovelenov
Staff

Hi,
I believe we might need to implement performance preference setting in the init puzzle. It might not work in all cases but still better than nothing. Adding this task to our TODO list.

Soft8Soft Tech Chief
X | FB | LinkedIn

2021-11-12 at 5:21 pm #46930

Yorick
Customer

Hi Alexander,
are you refering to powerPreference: 'highPerformance' or to something else?
Is it something we could manually set in the file at the moment?

2021-11-13 at 11:24 am #46934
Alexander Kovelenov
Staff
Yep, you can insert WebGL context attributes in the main JS file of your application (right before App constructor):
```
    ctxSettings.powerPreference = 'high-performance';

    var app = new v3d.App(CONTAINER_ID, ctxSettings, preloader);
    if (initOptions.useBkgTransp) {
        app.clearBkgOnLoad = true;
        app.renderer.setClearColor(0x000000, 0);
    }
```
Soft8Soft Tech Chief
X | FB | LinkedIn
2021-11-16 at 11:34 am #46982

Yorick
Customer

some feedback:
when we set ctxSettings.powerPreference = ‘high-performance’;
it makes it unusable on different machines with only integrated GPUs available to the browser
(you can check which GPUs are available to the browser with this code: https://jdashg.github.io/misc/webgl/low-power.html)
AND it also creates some artifacts
it’s really unusably slow, even though it works OK without powerPreference = ‘high-performance’;

So it seems like setting that powerPreference uses a lot more GPU resources (too much for an integrated GPU in our case)

When the browser has access to a dedicated GPU for high performance (again, you can check like this: https://jdashg.github.io/misc/webgl/low-power.html) then it does work fine

2021-11-16 at 12:33 pm #46983

Alexander Kovelenov
Staff

That’s really strange! What is the system that causes freezes and artifacts on ctxSettings.powerPreference = ‘high-performance’?

Soft8Soft Tech Chief
X | FB | LinkedIn

2021-11-16 at 1:35 pm #46991

Yorick
Customer

both on my laptop (dell xps 15):
windows 10 pro
intel i7 8750H
16GM RAM
intel UHD 630
GeForce GTX 1050 Ti

and my cellphone (Oneplus Nord):
Android 11
Qualcomm SM7250 Snapdragon 765G
12GB RAM
Adreno 620

important fact:
on my pc the browser doesn’t report the discrete GPU when visiting https://jdashg.github.io/misc/webgl/low-power.html
but only the integrated one for both “low-power” and “high-performance”

on my cellphone it mentions the Adreno 620 for both “low-power” and “high-performance”

2021-11-17 at 8:41 am #47003

Alexander Kovelenov
Staff

Looks like this feature is formally supported, but actually ignored in Chrome (and it appears so it does not work in other browsers too). So there are two choices remain:

1) optimize scene for low-end Intel GPU (for example by using the check performance puzzle)

2) detect low-end GPU and report to the user along instructions how to switch to discrete graphics.

Soft8Soft Tech Chief
X | FB | LinkedIn
Author

Posts