Announcement

Collapse
No announcement yet.

Geometric Picking Finally Lands In GNOME/Mutter 3.34 For Lowering CPU Usage

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Geometric Picking Finally Lands In GNOME/Mutter 3.34 For Lowering CPU Usage

    Phoronix: Geometric Picking Finally Lands In GNOME/Mutter 3.34 For Lowering CPU Usage

    In addition to Mutter seeing today an important last minute performance fix for the NVIDIA proprietary driver, Mutter also saw a long-standing performance optimization finally land for GNOME 3.34 that benefits all hardware/drivers...

    http://www.phoronix.com/scan.php?pag...metric-Picking

  • #2
    This one is particular interesting because it fixes GL pipeline stalls when the surface below the pointer got repainted..such as in games. So this one makes mouse movements in games much more smooth, which is usually not covered in automated benchmarks. Heads up to all involved to get this one merged, despite all the difficulties!

    Comment


    • #3
      Love it

      Comment


      • #4
        Nice that it was finally wrapped up!

        Comment


        • #5
          Originally posted by treba View Post
          This one is particular interesting because it fixes GL pipeline stalls when the surface below the pointer got repainted..such as in games. So this one makes mouse movements in games much more smooth, which is usually not covered in automated benchmarks. Heads up to all involved to get this one merged, despite all the difficulties!
          What "color picking operations" are going on while moving the mouse and playing an OpenGL game??

          Comment


          • #6
            The Canonical dev's contributions in that thread are a masterpiece of patience and control, as it took a year and lots of obstruction to get the patch merged,despite overwhelming evidence in his favour.

            Comment


            • #7
              Originally posted by timrichardson View Post
              The Canonical dev's contributions in that thread are a masterpiece of patience and control, as it took a year and lots of obstruction to get the patch merged,despite overwhelming evidence in his favour.
              If you get paid for what you're doing it makes a world of a difference.

              Comment


              • #8
                timrichardson Vanvugt is difficult as well. So many bad commit messages, so many closed MRs, so many untested MRs. All claimed to help performance.

                Maintaining complex code like a wayland compositor is super tough work. If people keeps spamming bad MRs then they get told to up their game. Hand that amount of bad code to Linus and he would murder you by words.

                Mutter is used on enterprise class distributions. You can’t allow that to regress. Remember Canonical ran mir and unity8 into the ground. Vanvugt is part of this failure. Mutter Upstream is here to discriminate against crazy. And they do a good job.

                That said they could treat vanvugt much better. He is like the only guy who work full time on performance.

                Comment


                • #9
                  144Hz Van Vugts patches also tend to just come out of no where with no involvement of other developers, thus step on the other developers work (Van Vugt isn't a member of the GNOME Foundation), changes things without realising they were done that way for a reason or have severe regressions (as a recent one that got reverted did).

                  People complain GNOME is buggy, yet also complain that third-party MRs with no community involvement aren't just accepted without scrutiny.
                  Last edited by Britoid; 09-03-2019, 12:13 AM.

                  Comment


                  • #10
                    After half a year of development, Compiz in 2006 (13 years ago) was prettier, snappier, and less memory and CPU intensive than GNOME3/mutter is today despite GNOME3/Mutter being developed for 8 years. Just imagine how great the Linux desktop would be if David Reveman had continued working on it, rather than working on ChromeOS...

                    Comment

                    Working...
                    X