<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - With Vsync disabled, Weston almost halves *visible* frame update rate, compared to X desktop"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106736#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - With Vsync disabled, Weston almost halves *visible* frame update rate, compared to X desktop"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106736">bug 106736</a>
from <span class="vcard"><a class="email" href="mailto:ppaalanen@gmail.com" title="Pekka Paalanen <ppaalanen@gmail.com>"> <span class="fn">Pekka Paalanen</span></a>
</span></b>
<pre>weston-simple-egl is also extremely fast to render (one triangle!), it doesn't
put any load on the GPU. If you don't throttle it at all, on my intel desktop
it runs at 12000 fps in its default size. So it makes sense it cannot reproduce
the problem, because it cannot block the compositor in its GPU task.
Until we can have the GPU preempted when the compositor's high-priority GPU job
becomes runnable, I don't think the situation can get any better for abusive
(SwapInterval=0) applications.</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>