[Bug 96820] intel-virtual-output: bad performance

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=96820

--- Comment #3 from Chris Wilson <chris at chris-wilson.co.uk> ---
(In reply to main.haarp from comment #2)
> Created attachment 124936 [details]
> 5000 lines of ivo -v log
> 
> Thanks.
> 
> I've ran ivo with the -v flag while attaching two 2560x1440 monitors over
> DP. This produces quite a lot of log, I've attached it.
> 
> However I can't find any hints regarding being rate-limited. What exactly am
> I looking for?

I actually thought there was more timing info in there, but it's the frequency
and duration of the rendering and its synchronisation that's important.

> I've also played with virtualgl vs. primus, but did not notice a difference
> between the two. ivo uses its own independent method of copying between X
> servers, correct?

ivo is just using plain X (which iirc virtualgl and primus also do). What I am
hoping for is for nvidia to support DRI3/Present as that would give a very
simple way to do efficient transfers. Alternatively using glMapBuffer() may
fare better (although it should not from a technical standpoint).

The first step you may want to try is to stop your desktop wm from marking the
whole framebuffer as being damaged on every frame.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160706/138ef696/attachment.html>