[Wayland-bugs] [Bug 106736] Weston almost halves *visible* frame update rate from what application actually produces

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=106736

Eero Tamminen <eero.t.tamminen at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         QA Contact|xorg-team at lists.x.org       |
            Summary|Xwayland halves *visible*   |Weston almost halves
                   |screen update rate          |*visible* frame update rate
                   |                            |from what application
                   |                            |actually produces
          Component|XWayland                    |weston

--- Comment #5 from Eero Tamminen <eero.t.tamminen at intel.com> ---
This is Weston issue.  It happens also with native Weston applications.


When testing this on Broxton...

> [core]
> repaint-window=N

With a Wayland native 3D benchmarking application that updates its window at
65-70 FPS...

Repaint value, Weston average update FPS:
-  1: 30 FPS
-  3: 30-35 FPS
-  5: 35-40 FPS
-  7: 40-45 FPS
-  9: 40-50 FPS
- 11: 45-55 FPS
- 13: 50-60 FPS
- 15: 60 FPS

When application runs through Xwayland, the situation is pretty similar.

When application runs below 60 FPS, there's a similar issue.  Application
running at 27 FPS, drops to 15 FPS with default repaint-window value "7", and
it needs to be at least "13" for Weston updates to happen at 20 FPS (= what it
should be).

-> Seems that Weston repaint-window option should default to 15.


What it actually does, and why it currently defaults to lower value?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-bugs/attachments/20180601/b5ec349f/attachment.html>