(In reply to Vincent from bug 1617498 comment 15) > Robert I have a 4K display running off Intel UHD 620 graphics (Whiskey lake). Do you know of a good (scientific) profiling utility for GNOME/Fedora so I could do some testing? Perhaps there's a way of logging intel_gpu_top output to a file. Unfortunately I don't now much about this yet. Two things that may be helpful are the Firefox internal profiler[1] and Sysprof for Gnome-Shell/Mutter[2] to find hotspots, but that's maybe not what you are looking for. > I see in [this blog](https://mozillagfx.wordpress.com/2019/10/22/dramatically-reduced-power-usage-in-firefox-70-on-macos-with-core-animation/) macOS has a tool to show the area being repainted. Are you aware of such a tool on Linux/Wayland? Gnome has some inbuild tools, but they are not yet accessible via a nice app (hopefully in the future[3]). If you open looking glass via `alt`+`f2` -> `lg` -> `enter`, you can enable some debug overlays: - damage region: `Meta.add_clutter_debug_flags(0, Clutter.DrawDebugFlag.PAINT_DAMAGE_REGION, 0)` / `Meta.remove_clutter_debug_flags(0, Clutter.DrawDebugFlag.PAINT_DAMAGE_REGION, 0)` - opaque regions: `Meta.add_debug_paint_flag(Meta.DebugPaintFlag.OPAQUE_REGION)` / `Meta.remove_debug_paint_flag(Meta.DebugPaintFlag.OPAQUE_REGION)` 1: https://profiler.firefox.com/ 2: https://blogs.gnome.org/chergert/2020/03/15/how-to-use-sysprof-to-part-ii/ 3: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3968
Bug 1717902 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Vincent from bug 1617498 comment 15) > Robert I have a 4K display running off Intel UHD 620 graphics (Whiskey lake). Do you know of a good (scientific) profiling utility for GNOME/Fedora so I could do some testing? Perhaps there's a way of logging intel_gpu_top output to a file. Unfortunately I don't now much about this yet. Two things that may be helpful are the Firefox internal profiler[1] and Sysprof for Gnome-Shell/Mutter[2] to find hotspots, but that's maybe not what you are looking for. > I see in [this blog](https://mozillagfx.wordpress.com/2019/10/22/dramatically-reduced-power-usage-in-firefox-70-on-macos-with-core-animation/) macOS has a tool to show the area being repainted. Are you aware of such a tool on Linux/Wayland? Gnome has some inbuild tools, but they are not yet accessible via a nice app (hopefully in the future[3]). If you open looking glass via `alt`+`f2` -> `lg` -> `enter`, you can enable some debug overlays: - damage region: `Meta.add_clutter_debug_flags(0, Clutter.DrawDebugFlag.PAINT_DAMAGE_REGION, 0)` / `Meta.remove_clutter_debug_flags(0, Clutter.DrawDebugFlag.PAINT_DAMAGE_REGION, 0)` - opaque regions: `Meta.add_debug_paint_flag(Meta.DebugPaintFlag.OPAQUE_REGION)` / `Meta.remove_debug_paint_flag(Meta.DebugPaintFlag.OPAQUE_REGION)` P.S.: note that the damage region overlay currently shows any damage done in Mutter - not just surface damage reported by the client. That means if Firefox moves a tile via Wayland APIs but doesn't repaint the content, the whole area will still get repainted. We don't yet have a indicator for pure client surface/buffer damage in Gnome. 1: https://profiler.firefox.com/ 2: https://blogs.gnome.org/chergert/2020/03/15/how-to-use-sysprof-to-part-ii/ 3: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3968
(In reply to Vincent from bug 1617498 comment 15) > Robert I have a 4K display running off Intel UHD 620 graphics (Whiskey lake). Do you know of a good (scientific) profiling utility for GNOME/Fedora so I could do some testing? Perhaps there's a way of logging intel_gpu_top output to a file. Unfortunately I don't now much about this yet. Two things that may be helpful are the Firefox internal profiler[1] and Sysprof for Gnome-Shell/Mutter[2] to find hotspots, but that's maybe not what you are looking for. > I see in [this blog](https://mozillagfx.wordpress.com/2019/10/22/dramatically-reduced-power-usage-in-firefox-70-on-macos-with-core-animation/) macOS has a tool to show the area being repainted. Are you aware of such a tool on Linux/Wayland? Gnome has some inbuild tools, but they are not yet accessible via a nice app (hopefully in the future[3]). If you open looking glass via `alt`+`f2` -> `lg` -> `enter`, you can enable some debug overlays: - damage region: `Meta.add_clutter_debug_flags(0, Clutter.DrawDebugFlag.PAINT_DAMAGE_REGION, 0)` / `Meta.remove_clutter_debug_flags(0, Clutter.DrawDebugFlag.PAINT_DAMAGE_REGION, 0)` - opaque regions: `Meta.add_debug_paint_flag(Meta.DebugPaintFlag.OPAQUE_REGION)` / `Meta.remove_debug_paint_flag(Meta.DebugPaintFlag.OPAQUE_REGION)` P.S.: note that the damage region overlay currently shows any damage done in Mutter - not just surface damage reported by the client. That means if Firefox moves a tile via Wayland APIs but doesn't repaint the content, the whole area will still get repainted. We don't yet have a indicator for pure client surface/buffer damage in Gnome. OTOH, Firefox has overlays for this build in somewhere. 1: https://profiler.firefox.com/ 2: https://blogs.gnome.org/chergert/2020/03/15/how-to-use-sysprof-to-part-ii/ 3: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3968