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 582801 - compositing causes high CPU with xv
compositing causes high CPU with xv
Status: RESOLVED DUPLICATE of bug 562669
Product: metacity
Classification: Other
Component: general
2.26.x
Other All
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2009-05-15 18:02 UTC by rdavis
Modified: 2009-11-18 18:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description rdavis 2009-05-15 18:02:43 UTC 
Please describe the problem:
Stumbled onto the problem tracking down another problem.  I have a 1280x720 h264 video I am playing with mplayer.  With metacity compositing activated the X process shoots up to 80+% (1 core I assume since total CPU was 60%).  Mplayer with the x11 driver (-vo x11) causes this to drop to 30+%.  Disabling compositing drops the X process to 1-5%.  I also tried compiz and the X process stayed under 10%.

E6320 Core2 Duo
Intel 965G
Gentoo

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Owen Taylor 2009-11-18 18:46:56 UTC 
Unredirecting fullscreen windows is really the only meaningful way to make things much better, though there might be some small incremental improvement possible in the xrender compositor's algorithms.

(Nobody is working on the xrender compositor at all in any case; way forward for compositing is via GL, either with Compiz or with Mutter.)

*** This bug has been marked as a duplicate of bug 562669 ***