<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> <span class="fn">Eero Tamminen</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Weston almost halves *visible* frame update rate from what application actually produces"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106736">bug 106736</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">QA Contact</td>
<td>xorg-team@lists.x.org
</td>
<td>
</td>
</tr>
<tr>
<td style="text-align:right;">Summary</td>
<td>Xwayland halves *visible* screen update rate
</td>
<td>Weston almost halves *visible* frame update rate from what application actually produces
</td>
</tr>
<tr>
<td style="text-align:right;">Component</td>
<td>XWayland
</td>
<td>weston
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Weston almost halves *visible* frame update rate from what application actually produces"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106736#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Weston almost halves *visible* frame update rate from what application actually produces"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106736">bug 106736</a>
from <span class="vcard"><a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> <span class="fn">Eero Tamminen</span></a>
</span></b>
<pre>This is Weston issue. It happens also with native Weston applications.
When testing this on Broxton...
<span class="quote">> [core]
> repaint-window=N</span >
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?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>