Page 1 of 5 123 ... LastLast
Results 1 to 10 of 44

Thread: KWin Can Cause A Performance Hit Too

  1. #1
    Join Date
    Jan 2007
    Posts
    14,327

    Default KWin Can Cause A Performance Hit Too

    Phoronix: KWin Can Cause A Performance Hit Too

    Last week we published Arch Linux vs. Ubuntu benchmarks to finally lay to rest that for the overall system performance the speed of the rolling Arch Linux distribution is not too different from that of Ubuntu when running with similar package versions. One of the areas, however, where the performance was different with the "out of the box" experience was the OpenGL gaming where Ubuntu was using Compiz by default where as Arch had Metacity. This surprised many so we published another article entitled The Cost Of Running Compiz where we showed the performance penalties of a compositing window manager with different hardware and drivers. This led some to ask whether the performance of KWin also causes the OpenGL frame-rate to drop, so here are those KDE benchmarks.

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

  2. #2
    Join Date
    Apr 2008
    Posts
    42

    Default

    Judging by the results, perhaps the title should be changed to:
    The Cost of Running Compositing on NVIDIA drivers.

    Looks like ATI and Intel actually BENEFIT from compiz or kwin in most cases. From this, we can deduce it is not compiz or kwin reducing performance but compositing on Nvidia.

  3. #3
    Join Date
    Nov 2008
    Posts
    18

    Default

    Could you rerun the nVidia test with their newly released 256 series beta drivers?

    I seem to remember kwin having an option to disable compositing for fullscreen windows too, which perhaps could make life a bit easier for users with nvidia+kde+gaming.

  4. #4
    Join Date
    Sep 2008
    Posts
    332

    Default

    for me kwin effects are really slow and choppy with fglrx.
    compiz on the other hand runs smooth
    (im using the backclear patch)

  5. #5
    Join Date
    Mar 2010
    Posts
    60

    Default

    I really would be interested in seeing if the speed ups with compositing is because the cards are being dynamically clocked.

    By this i mean if the catalyst driver is maintaining a higher clock speed when compositing in order to cope and as a side effect is making the game run faster.

    An interesting read anyhow.

  6. #6
    Join Date
    Dec 2007
    Location
    Edinburgh, Scotland
    Posts
    574

    Default

    Is it possible to add a base line ie without compositing to see how much of a negative impact it makes

  7. #7
    Join Date
    Nov 2008
    Posts
    762

    Default

    Quote Originally Posted by andrnils View Post
    I seem to remember kwin having an option to disable compositing for fullscreen windows too
    yes, I remembered something like that, too. See here:

    http://www.kdedevelopers.org/node/3639
    Second improvement is unredirecting fullscreen windows - that is, if a fullscreen window is not covered by something else, such as a game or a movie, that window is excluded from compositing and allowed to draw normally. This lets it draw at the full speed and should also help with avoiding tearing.
    has been implemented almost 2 years ago.

    So either this feature was disabled during the tests, or it didn't work in some cases. Interesting.

  8. #8
    Join Date
    Dec 2009
    Location
    Italy
    Posts
    174

    Default

    As I posted under the compiz thread, unredirect of fullscreen windows has to be manually enabled in ~/.kde/share/config/kwinrc in kde4. For me (nvidia proprietary driver) it solves choppiness issues when running Unigine.

  9. #9
    Join Date
    Jun 2008
    Posts
    29

    Default

    Does the performance hit occur if the desktop effects are disabled too? Or is it linked to the effects?

  10. #10

    Default

    Quote Originally Posted by andrnils View Post
    I seem to remember kwin having an option to disable compositing for fullscreen windows too, which perhaps could make life a bit easier for users with nvidia+kde+gaming.
    This is an option or this should work out of the box?

    There's usually no PulseAudio running in KDE, so games should be even a bit faster compared to Gnome + PulseAudio.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •