-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebGL performance issues #4279
Comments
cc: @kjozwiak |
@PhilT would you be able to try this again on our latest Nightly version? We did some config changes which may help 😄 |
Hi @bsclifton, unfortunately performance is the same. Still down at around 10fps (I've changed the test a bit so fps has dropped but it's same on Stable) on my test whereas Chrome is getting about 45fps. Tested on Version 0.69.24 Chromium: 75.0.3770.100 (Official Build) nightly (64-bit) that I just installed. |
Details from Same user running |
Ran the above test on my machine - definitely leads me to think it's a driver/config issue. Something triggers the difference in config change and that seems to have a direct impact on the score FWIW, here are the scores I got on my workstation:
@PhilT can you visit chrome://gpu both in Brave and Chrome and use the handy For folks reading this- there are definitely some known GPU issues with Brave. Seems to be config specific for each type of problem (GPU taking too much power, bad webGL performance, artifacts drawn on screen), so I'm doing some detective work and cataloging the data here: |
@bsclifton not sure if helpful, but here are my results on two different machines which had similar scores. I didn't see any large discrepancies between the two browsers on those particular machines. Probably related to GPU drivers as you pointed out above:
|
So, I've just run my own test on my new machine and I get the same result in both Chrome, Chromium and Brave. All about 10-11fps (1 million cubes on the screen). Kinda annoyed as the new machine, a Razer Blade Pro RTX 2060, cost a lot and is not performing the same as my 2 year old Blade 14! However, it does mean the config must be off. I'm gonna have a dig around to try to find some guides on how to optimize the setup. If you have anything that might help config-wise, I'd be happy to try it. I'll run the performance test as well, when I get a moment. |
Okay, so I'm a bit of an idiot and forgot to set nVidia as the card to use when running Chrome/Brave. So now I'm getting around 30fps on all 3 browsers with Chromium actually hitting about 33-34 oddly. This is still less than my other machine which technically has an older, slower(?) graphics card. 10-15fps is still a pretty big gap so I'll do some more digging when I have time. |
So this is better.
I'll run some more tests and grab some averages. |
I've run the benchmark a few more times and I'm getting consistently lower scores on the nightly build than either Brave stable or Chromium. However, the numbers do vary a bit (lows of 1195 on Nightly and highs of 1327 on stable). However, maybe those optimisations are helping some GPUs and hindering others. |
Closing as unfortunately there aren't any clear steps to investigate or debug this issue. Also no folks giving a +1 or creating similar issues. I ran again to just check and things look good:
|
Performance of WebGL compared with Chrome and Chromium is subpar
Whilst playing around with some WebGL 2 code I noticed that fps seemed to be roughly half of what Chrome was chucking out. Rendering 2 million cubes produced around 29fps whilst in Chrome it easily hit 60fps.
So I ran some more tests with a proper benchmark site https://web.basemark.com. These were all run on my Razer Blade 14 (2017) running Windows 10 x64.
Here are my results:
These confirmed my suspicions and is quite substantial.
I did notice that Chrome has some additional Driver Bug Workarounds under
chrome://gpu
And one additional one in Brave Release:
If I had to guess I'd say this could be related to having a laptop with Intel and NVIDIA graphics cards. Those options that have been toggled above look like they're related to picking the wrong card. But it's just a guess.
Happy to provide more info or do more tests if needed.
The text was updated successfully, but these errors were encountered: