Page 5 of 5 FirstFirst ... 345
Results 41 to 45 of 45

Thread: The First Wayland Benchmarks From Fedora 20 Show Great Promise

  1. #41
    Join Date
    Oct 2011
    Location
    Rural Alberta, Canada
    Posts
    1,058

    Default

    Quote Originally Posted by edoantonioco View Post
    I just hope than wayland support will be as easy as a simple new feature in an update of the game, and not to port the games almost from 0 again to be able to play it in wayland, in that case, valve would not be happy, because all their work is in the currently state of linux (and the same for the other people than had ported games to linux).
    As far as I am aware this should mostly be handled by the abstraction layers being used, such as SDL.

  2. #42
    Join Date
    Jul 2012
    Location
    SuperUserLand
    Posts
    538

    Default

    the difference being this is barely usable, even OP stated that it crashed and it was hell to get it to work


    for Xmir I can't say I had a single crash or show stopping bug

  3. #43
    Join Date
    Sep 2012
    Posts
    792

    Default

    Quote Originally Posted by Pallidus View Post
    the difference being this is barely usable, even OP stated that it crashed and it was hell to get it to work


    for Xmir I can't say I had a single crash or show stopping bug
    But then, you hadn't a Mir shell and compositor either, so what's the point?

  4. #44
    Join Date
    Mar 2013
    Posts
    187

    Default

    The reasons to replace Xorg are well know, listed here.
    Some months yet and I will use a well done display server.

  5. #45
    Join Date
    Dec 2012
    Posts
    172

    Default

    As an additional comment, we found that Weston causes a useless copy (X compositing) because the X decoration window it uses for X application has different visual than the application. That means X has to do an additional copy. (That's going to be fixed)

    After looking closer at the figures, the performance hit of Gnome XWayland is not due to a similar issue. It isn't an overhead for every frame, but a constant overhead per second.
    drago01 comments tells that Gnome doesn't support yet bypassing Wayland compositing. It makes sense to say the performance hit observed is entirely due to this: all benchmarks run >= 60 fps, causing Wayland to composite 60 times per second (= constant overhead).

    Currently work is done to support vsync in XWayland (almost done), and (harder) respect the Wayland buffer release semantic, in the cases in which we can do it without impacting performance, to suppress tearings.
    It is also possible that performance increases if we manage to implement a DDX feature proposed by Chris Wilson a few years ago, implemented in the intel DDX, but whose patch to use the feature has not been merged in X yet (but maybe it will be merged with XWayland, who knows?).
    Last edited by mannerov; 10-12-2013 at 09:18 AM.

Posting Permissions

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