Announcement

Collapse
No announcement yet.

Qt/GTK Speed On Unity/KDE/Xfce/LXDE/GNOME/Razor

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

  • Qt/GTK Speed On Unity/KDE/Xfce/LXDE/GNOME/Razor

    Phoronix: Qt/GTK Speed On Unity/KDE/Xfce/LXDE/GNOME/Razor

    Shared earlier today were OpenGL game benchmarks under different Linux desktops. Now to complement those earlier results are 2D performance tests under Unity, KDE, GNOME Shell, Xfce, LXDE, and Razor-qt...

    http://www.phoronix.com/vr.php?view=MTMxNDk

  • #2
    LXDE looks really crappy here, what's going on? Can't see why openbox with LXDE's taskbar tanks performance like that... in fact, that seems outright wrong, like super bug wrong.

    XFCE on the other hand is about what I expect.

    Comment


    • #3
      Performance of desktop environments

      I would like to see benchmarks of Steam games (Half Life, Serious Sam3, Team Fortress 2, ...) for different desktop environments, especially Unity, Gnome, KDE and LXDE.
      From my experience, Unity is the desktop that give the lowest fps for any OpenGL game.

      As these games are mostly available for Linux, Windows and Mac OS, it may also be a good benchmark to compare graphics drivers for all 3 platforms.

      Comment


      • #4
        Michael: Benchmarking Compositors this way is pointless please go read this

        Comment


        • #5
          Originally posted by Phoronix
          Also holding their ground fairly well against Xfce were Unity with Compiz and LXDE while KDE, LXDE, and Razor-Qt were further back.
          (emphesis mine) You mean Gnome Shell?

          Comment


          • #6
            Originally posted by drago01 View Post
            Michael: Benchmarking Compositors this way is pointless please go read this
            1. the way it is done here it is not pointless at all
            2. your article is WAY too outdated. gnome shell with mutter is using unredirected for fullscreen already since a long time. in this article it still talks about a mutter without that.

            Comment


            • #7
              It is well known that compositing hurts framerates in games. For DEs where compositing can be toggled on/off, both options should be tested to get a fuller picture.

              Comment


              • #8
                Was the KDE system configured properly?

                Comment


                • #9
                  Originally posted by ultimA View Post
                  It is well known that compositing hurts framerates in games. For DEs where compositing can be toggled on/off, both options should be tested to get a fuller picture.
                  You are absolutely right...both should be tested. Now that article doesn't give any answers for me. At the moment I have marked programs like mplayer and steam automatically toggle compositing off. With those settings games runs fast and videos without tearing on KDE.

                  Comment


                  • #10
                    Isn't QGears2 GLORIFIED "Do I have OpenGL AT ALL?" ???

                    Comment


                    • #11
                      Originally posted by a user View Post
                      1. the way it is done here it is not pointless at all
                      2. your article is WAY too outdated. gnome shell with mutter is using unredirected for fullscreen already since a long time. in this article it still talks about a mutter without that.
                      That article only meantion Gnome Shell as NOT BEING TESTED.

                      Comment


                      • #12
                        Originally posted by a user View Post
                        1. the way it is done here it is not pointless at all
                        2. your article is WAY too outdated. gnome shell with mutter is using unredirected for fullscreen already since a long time. in this article it still talks about a mutter without that.
                        1. It isn't most of this benchmarks are not fullscreen and therefore the FPS they report might not be the FPS they actually draw on screen (please read the (non outdated) article).
                        2. I know (I wrote that code after all) but this is irrelevant see 1.

                        Also unredirected windows should have more or less the same performance everywhere assuming no background work taking up resources.

                        Comment


                        • #13
                          Originally posted by e8hffff View Post
                          Was the KDE system configured properly?
                          Yes, that result did surprise me. Running the test locally points towards a pixmap leak in the GTK+ oxygen-gtk theme - performance is trashed when you are running from swap. Assuming that the KDE system is configured similarly, ofc.

                          Comment


                          • #14
                            Originally posted by przemoli View Post
                            Isn't QGears2 GLORIFIED "Do I have OpenGL AT ALL?" ???
                            Hmm. The QGears2 is not a very good benchmark in that the Image/Render/GL are not comparable and thanks to Qt do not measure what you think. The GL variant of the benchmark has no antialiasing, sacrificing visual quality for speed. That would be reasonable if the other two methods were also configured similarly. The Qt Render backend does all the rasterisation in the client on the CPU before sending images to X and compositing them. Qt does not have a fast raster engine, and this entirely misses the point of using the GPU to do the operations for which it is extremely fast. In essence, the Render backend is just a slow way of acting like its Image backend. If Qt were any good at all, the Render backend should be faster than the GL backend for all operations.

                            Comment


                            • #15
                              Unity seems to be mature and performing well. It only took 2 years of public beta testing

                              Better late than never i guess..

                              Comment

                              Working...
                              X