Announcement

Collapse
No announcement yet.

Chrome Enables Its GPU Scheduler By Default

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

  • Chrome Enables Its GPU Scheduler By Default

    Phoronix: Chrome Enables Its GPU Scheduler By Default

    The latest Google Chromium Git code has enabled its GPU scheduler by default...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    First thing... I think yay, GPU decode... sadly bad see, it only GPU scheduler.

    Anyway anyone know more about GPU Decode?

    Comment


    • #3
      Originally posted by xpris View Post
      First thing... I think yay, GPU decode... sadly bad see, it only GPU scheduler.

      Anyway anyone know more about GPU Decode?
      It's not enabled by default but it works fine in Chrome AFAIK? Check some stuff in chrome://flags and chrome://gpu . Firefox doesn't have it though.

      Comment


      • #4
        Originally posted by ernstp View Post

        It's not enabled by default but it works fine in Chrome AFAIK? Check some stuff in chrome://flags and chrome://gpu . Firefox doesn't have it though.
        Nah... In Chrome is force disabled. Even If we change flags to allow hadware acceleration - it won't work. OFC chrome:gpu show all gpu options on green but it now work.

        But code is here. We can use it but only in Chromium if we compile it by self with extra flags enabled. Then it work. We have Chromium DEV ppa for Ubuntu with enabled HW decode for Linux but this is not officially and main Chrome or even Chromium from official distro repository still lack this feature.

        Comment


        • #5
          Originally posted by xpris View Post

          Nah... In Chrome is force disabled. Even If we change flags to allow hadware acceleration - it won't work. OFC chrome:gpu show all gpu options on green but it now work.

          But code is here. We can use it but only in Chromium if we compile it by self with extra flags enabled. Then it work. We have Chromium DEV ppa for Ubuntu with enabled HW decode for Linux but this is not officially and main Chrome or even Chromium from official distro repository still lack this feature.

          Comment


          • #6
            Yeah.... now if only they could stop unlocking the Gnome Keyring hundreds of times and causing my ip address to get blacklisted as a result of too many authentication attempts that would be great...

            Honestly, the whole concept that a browser gets its fingers into so many pots like PDF viewing, bookmarking, netflix, music playing, etc... is annoying.

            These days there is a purity to using a simple browser with 0 extra features and the shit just works instead of takes 4 minuts to start due to some BS sync with Google Server.

            Comment


            • #7
              Off topic, but looking at the title, I suddenly realized how for us, geeks, a code commit means "Chrome enables feature X", even if the general public won't see this for a couple of months. Just a reminder of how big a disconnection is between our worlds.

              Comment


              • #8
                Maybe they should fix Chrome's vsync for 120Hz first. It's completely broken and unusable. Scrolling is a stuttery clusterfsck, and so is watching youtube.

                Maybe we should start a charity and donate a 120Hz monitor to Google Linux Chrome team, since they don't seem to have the funds, the poor fellas.

                Comment


                • #9
                  Originally posted by RealNC View Post
                  Maybe they should fix Chrome's vsync for 120Hz first. It's completely broken and unusable. Scrolling is a stuttery clusterfsck, and so is watching youtube.

                  Maybe we should start a charity and donate a 120Hz monitor to Google Linux Chrome team, since they don't seem to have the funds, the poor fellas.
                  Is that a confirmed Chrome issue? Because vsync should be something handled by some underlying framework.

                  Comment


                  • #10
                    Originally posted by bug77 View Post

                    Is that a confirmed Chrome issue? Because vsync should be something handled by some underlying framework.
                    Yes, it's a Chrome issue. The team even said on the Chromium bugtracker that they don't have a monitor to develop on. They only have 60Hz.

                    Poor, poor Google.

                    Comment

                    Working...
                    X