<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [SNB/IVB DRI3] OSD's from Gnome-shell hangs or crashes the Intel driver"
href="https://bugs.freedesktop.org/show_bug.cgi?id=76321#c19">Comment # 19</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [SNB/IVB DRI3] OSD's from Gnome-shell hangs or crashes the Intel driver"
href="https://bugs.freedesktop.org/show_bug.cgi?id=76321">bug 76321</a>
from <span class="vcard"><a class="email" href="mailto:martin.kamleithner@gmail.com" title="martin.kamleithner@gmail.com">martin.kamleithner@gmail.com</a>
</span></b>
<pre>(In reply to Eero Tamminen from <a href="show_bug.cgi?id=76321#c18">comment #18</a>)
<span class="quote">> Main performance difference between DRI2 & DRI3 should come only in
> synthetic benchmarks where you go much over 60 FPS, with Vsync it should not
> be visible to user. That was about memory overhead and how perf is visible
> to the application.
>
> There are also differences in how frames get to screen after application has
> rendered them to the double/triple buffer.</span >
You are right, the performance difference is not from DRI2 vs DRI3, but from
SNA vs UXA: Switching back to UXA brings back good performance, but
reintroduces the bug.
The performance drop is not 100% reproduceable, it only happens on fullscreen
and only sometimes with various games (E.g. Binding of Isaac:Rebirth, Super
Hexagon), but when it happens, it is very noticeable (below 30 fps).
I don't know how to measure fps on Linux, but the fps drop is definitely there.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>