<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - KDE Konsole very slow scrolling with TearFree and QT graphics system native"
href="https://bugs.freedesktop.org/show_bug.cgi?id=77436#c170">Comment # 170</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - KDE Konsole very slow scrolling with TearFree and QT graphics system native"
href="https://bugs.freedesktop.org/show_bug.cgi?id=77436">bug 77436</a>
from <span class="vcard"><a class="email" href="mailto:absorbb@gmail.com" title="Ildar Nurislamov <absorbb@gmail.com>"> <span class="fn">Ildar Nurislamov</span></a>
</span></b>
<pre>Considering the fact that scrolling is already 95% perfect - no difference was
noticed. Red spikes on its places.
(In reply to <a href="show_bug.cgi?id=77436#c169">comment #169</a>)
<span class="quote">> Yeah. On my GT2 + dual-channel aa==rgb, whereas on my GT1 + single-channel
> aa==1.5*rgb.
>
> That means I am memory bound with single-channel, but compute bound with
> dual-channel. I think. Will have to ponder a little bit more, because
> despite that, my baby ivb is still 10% faster than yours. </span >
And your GT2 is 2.5faster than mine
<span class="quote">> But back to the bigger question... How does the system behave now when
> scrolling?</span >
Considering the fact that scrolling is already 95% perfect - no difference was
noticed. Red spikes are still on its places.</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>