After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 738276 - Vaapisink and SNA acceleration with dual screen configuration produce high CPU
Vaapisink and SNA acceleration with dual screen configuration produce high CPU
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gstreamer-vaapi
unspecified
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-10-10 07:15 UTC by radojko
Modified: 2017-08-09 09:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description radojko 2014-10-10 07:15:09 UTC 
Vaapi sink and SNA acceleration with Option "TearFree" "true" on dual screen monitor configuration produce high CPU when two large videos(near full screen and full screen - 1920x1080)are played.
Top command does not show high cpu but mpstat and iotop shows 100%. 

When "TearFree" is disabled or UXA acceleration is used instead SNA, CPU is low. 
Xvimagesink does not have this problem.

This problem is affected on different Intel processors: Celerons 1037, J1900, i3 Sandy and Ivy Bridge.
Ubuntu and Fedora are both affected.
Latest Intel driver are installed with Intel Graphics Installer 1.0.6 for Linux.
Comment 1 sreerenj 2016-03-24 16:55:44 UTC 
Moving to Product:GStreamer, Component:gstreamer-vaapi
Comment 2 Víctor Manuel Jáquez Leal 2017-03-14 15:33:48 UTC 
Is this still an issue?

In my opinion this is not in gstreamer-vaapi issue, but in the xorg driver.
Comment 3 Julien Isorce 2017-03-14 23:51:07 UTC 
Could you use linux perf tools (sudo perf record -a -p pid) to figure out what is causing a higher cpu usage ?
Comment 4 Víctor Manuel Jáquez Leal 2017-08-09 09:59:13 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!