[Bug 786054] mapping vaapi buffer slow

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=786054

--- Comment #6 from Víctor Manuel Jáquez Leal <vjaquez at igalia.com> ---
Created attachment 360184
  --> https://bugzilla.gnome.org/attachment.cgi?id=360184&action=edit
simplified test file

I had simplified a bit the test app and used callgrind to measure the CPU
consumption and the call graph.

The CPU consumption bottle neck are in memcopy and ffi calls. But in buffer
map, which means the va image load, what I see is a lot mutex locking in the
Intel driver.

I don't know the internal of the driver, but it might have a single list of
buffers, and when there is concurrent pipelines decoding, it would take
increasing time to lock, find a process, the surface to dump as image.

This would mean that the driver should be improved for this use-case. So, what
I would recommend is to fill an issue in intel-vaapi-driver in github:

https://github.com/01org/intel-vaapi-driver/issues

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.