<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Shared Memory queuing up in xlib backend for slow X Server 1.9.5"
href="https://bugs.freedesktop.org/show_bug.cgi?id=75524#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Shared Memory queuing up in xlib backend for slow X Server 1.9.5"
href="https://bugs.freedesktop.org/show_bug.cgi?id=75524">bug 75524</a>
from <span class="vcard"><a class="email" href="mailto:kasberger@heidenhain.de" title="kasberger@heidenhain.de">kasberger@heidenhain.de</a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=75524#c5">comment #5</a>)
<span class="quote">> My point is that the client is pushing data faster than the Xserver can
> render it, so the client is building up a massive output latency. It tends
> to cause very annoying lag. However, how to close that feedback loop is not
> obvious and may require an extra interface in cairo (something like
> cairo_device_throttle).</span >
Yes, I agree. But if a client should do active throtteling means the client
needs two things
a) intelligence when throtteling is useful. How to measure the speed of a
xserver?
b) intelligence how to throttle down
What about a kind of callback each time called when the cairo xlib backend
allocates/deallocate a shared memory arena? For the client it would be a good
hint there is something strange with xserver
Or can you think for other measuremnt parameters indicating a a xserver load ?
Oh I think I am too directly attached to my problem.
What about cairo_device_throttle_strategy(..) e.g. with NONE (=old behavior),
COWARD (=try to get in sync with xserver every time), BEST (=sync if really
needed) ?
Maybe second solution would be much better. What do you think?</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>