1744647 - Google maps very slow on 4k screen with Nvidia Quadro M2000M (Mate X11, Nvidia driver 495)

Status: RESOLVED DUPLICATE of bug 1735929

(Core :: Graphics: WebRender, defect, P3)

Description

[Nikolay Martynov]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:96.0) Gecko/20100101 Firefox/96.0

Steps to reproduce:

• Open FF on Linux on 4k screen with window covering the whole screen
• Go to google maps, into relatively populated area
• Switch to satellite view (3d)
• This will take quite some time to fully render
• zoom out a bit - it will take 10s of seconds to fully render
• zoom in - it will take 10 of seconds to fully refresh again

Network is not a problem - there is almost no network activity. WebContent process is pegged at 100+% CPU

Actual results:

Zoom in/out panning is very slow. More specifically - you can move/pan existing image just fine. Rendering 'new' bits is very slow.

If I reduce the window size to ~FHD equivalent there seems to be no problem

Expected results:

Zoom/pan of google maps should not be slow.

Enabling/disabling EGL and webrender doesn't seem to change anything.
Setup:
Ubuntu
FF nightly
Latest nvidia binary drivers,
GM107GLM [Quadro M2000M]

Problem has existed for a very long time

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Graphics: WebRender' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 2

[Darkspirit]

Thanks for the report!
Please capture a performance profile:

1. Open https://www.google.com/maps
2. Open https://profiler.firefox.com in another tab
3. Click on "Enable Firefox Profiler Menu Button"
4. Select "Graphics" in the Settings dropdown
5. Start Recording
6. Reproduce the problem on google maps (the first tab)
7. Click on the blue profiler button next to the main menu button to end the recording
8. Click on "Upload Locale Profile" and "Upload"
9. Post the https://share.firefox.dev/ url here on Bugzilla

Comment 3

[Nikolay Martynov]

https://share.firefox.dev/3lIhjGt

Comment 4

[Jeff Muizelaar [:jrmuizel]]

The profile doesn't have working symbols. Can you try again with a Firefox nightly build?

You may also want to try using the nouveau drivers to see if they give you better performance.

Comment 5

[Nikolay Martynov]

Hi.

This is firefox-nightly on ubuntu 21.04 with firefox-trunk-dbg and firefox-trunk-mozsymbols packages installed.
Is there anything else I need to install to get zymbols resolving?

Thanks!

Comment 6

[Jeff Muizelaar [:jrmuizel]]

Are you using a ubuntu packaged firefox nightly or one from here? http://ftp.mozilla.org/pub/firefox/nightly/2021/12/. You may need to use an official build from ftp.mozilla.org for it to work properly.

Comment 7

[Jeff Muizelaar [:jrmuizel]]

Can you also attach the graphics section of about:support?

Comment 8

[Darkspirit]

https://nightly.mozilla.org is the official and secure download page. Unfortunately, it doesn't provide a deb package, you need to extract the folder and run the firefox binary directly. (You might want to create your own Nightly.desktop file in ~/.local/share/applications.)

Comment 9

[Nikolay Martynov]

Attachment: Graphics from about:support

I was using nightly from ubuntu ppa

So I've downloaded from ttps://nightly.mozilla.org 

Here is the link to new profile: https://share.firefox.dev/3dtUIJc

Comment 10

[Nikolay Martynov]

To clarify: last profile was take with new, fresh user-profile in FF

Comment 11

[Darkspirit]

Please check if enabling "Force Composition Pipeline" in Nvidia X Server Settings > X Server Display Configuration > Advanced and restarting Nightly helps. (bug 1736245)

Comment 12

[Jeff Muizelaar [:jrmuizel]]

We're not reading back the WebGL content so this is expected to be slow. I'm not sure what the current expected status is on the Nvidia binary drivers and whether this should be working better there now.

Comment 13

[Darkspirit]

Slow WebGL is still expected on X11/Nvidia: bug 1735929
Slower OpenGL is still expected on X11/Nvidia (EGL=bug 1736245,workaround:Force Composition Pipeline. GLX=bug 1716049,workaround: gfx.swap-interval.glx=false).

(In reply to Nikolay Martynov)
Please also check if you are able to log in to Ubuntu Wayland. You might be able to select it in the bottom-right corner of the login screen.
Then start Nightly with $ MOZ_ENABLE_WAYLAND=1 ./firefox. Is Google Maps now smooth?
Nvidia Wayland support might have regressed between the 495 beta driver and 495 stable. It might work or not.

Comment 14

[Nikolay Martynov]

Couple of more data points:

I already have 'Option "ForceFullCompositionPipeline" "on"' in xorg.conf. Enabling composition pipeline has no effect on google maps performance - I have tried that.

I have tried with and without EGL (using gfx.x11-egl.force-enabled) - there is no noticeable perf difference.

Comment 15

[Nikolay Martynov]

When using nouveau performance is even worse (down to mouse movements being jerky) + there is a lot of blinking
When using nouveau + EGL FF shows artifacts and crashes.

Comment 16

[Nikolay Martynov]

I'm not able to try wayland at this point - I'm using Ubuntu Mate and I do not think it has wayland support.

Comment 17

[Nikolay Martynov]

Sorry for spamy messages, but I just wanted to make sure I provide all the information.
There is one more thing I should mention: the 'slow' part of this bug is, for lack of better term, slow process of 'detalization' of the image. Even on 4k screen I can comfortably move, zoom or even 'tilt' (i.e. 'pilot view') the scene. So the problem is not in FPS being low - FPS are actually quite comfortable.
The problem is that details of the scene (e.g. bits of the map that were not visible before) are very slow to appear. It is seems more details how up - slower it becomes. However 'movement' FPS doesn't change much.
Networking is not a problem - there is hardly any network activity going on and I have quite fast connection.
Please let me know if my explanation makes sense :).

Comment 18

[Nikolay Martynov]

I've tried running it on Wayland - if anything it makes experience worse. Although I must say that whole FF UI was sluggish on Wayland so maybe I was hitting some other issue.
I would like to also point out that FF on macOS doesn't have this problem and works very well with Google maps.

Comment 19

[Darkspirit]

510 beta: https://www.nvidia.com/Download/driverResults.aspx/184911/en-us

• Wayland: WebGL should be fast when starting Firefox with MOZ_ENABLE_WAYLAND=1 environment variable (bug 1749174) with Gnome Wayland on Ubuntu 22.04.
• X11: bug 1735929