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 496122 - Speed Issues in the Compositor
Speed Issues in the Compositor
Status: RESOLVED OBSOLETE
Product: metacity
Classification: Other
Component: Søren's compositor
2.21.x
Other All
: Normal minor
: ---
Assigned To: Metacity compositor maintainers
Metacity compositor maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-12 11:39 UTC by Christopher Roy Bratusek
Modified: 2008-02-11 20:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Christopher Roy Bratusek 2007-11-12 11:39:58 UTC 
Please describe the problem:
I just installed MCity 2.21.1 and wanted to test the compositor (which didn't work for me in v2.18), it works good, but there are some speed issues:

a) it's really slow then maximizing/unmaximizing/restoring windows
b) scrolling in firefox is really slow

Steps to reproduce:
1. compile mcity with --enable-compositor
2. enable compositor and restart mcity
3. do the actions, as described above


Actual results:
It's slow

Expected results:
It should been as fast as in 2D Mode

Does this happen every time?
Yes

Other information:
Comment 1 Thomas Thurman 2007-12-12 03:22:41 UTC 
Are you using the compositor in trunk, or the new one in the iains-blingtastic-bucket-o-bling branch?
Comment 2 Christopher Roy Bratusek 2008-02-11 20:22:11 UTC 
As I wrote this, I was using the old one, with the new one it's much better.
Comment 3 Christopher Roy Bratusek 2008-02-11 20:24:19 UTC 
iains-blingtastic-bucket-o-bling branch?. <- This is the one which has been merged into MCity, right?
Comment 4 Thomas Thurman 2008-02-11 20:28:43 UTC 
Yeah. Old references to IBBOB should be read as the modern trunk. Nothing should happen on IBBOB any more.
Comment 5 Christopher Roy Bratusek 2008-02-11 20:33:50 UTC 
ok. then we can close that issue.