On Sun, Aug 24, 2003 at 02:58:20AM +0200, Michel Dänzer scribbled: [snip] > > It seems that it allocates a pixmap for each window it manages (see ui.c, > > look for iw->pixmap) - at least that's how I understand the code. Also in > > ui.c in the meta_image_window_set function it seems that it does use that allocated > > previously pixmap as the window's backing store. > > AFAICT that code would only be used for the minimize effect, but that is > currently hardcoded to wireframe because the scaling is too slow. > > I'm afraid the problem is not what you think it is. That might very well be :). But it's a fact that metacity is much slower on my system than sawfish :( > > > > It's quite an annoying experience to actually see the desktop > > > > repainting on a fast machine (Athlon 2400+, 1GB RAM, Hercules Radeon > > > > 9000 128MB RAM)... I'm running XFree 4.3.0-0pre1v1 with > > > > xserver-xfree86-dri-trunk, compiled with athlon optimizations. > > > > > > Do the Slackware and Gentoo users you mention have a comparable setup? > > Yep, more or less the same. The gentoo one doesn't use the CVS dri xserver, > > the slackware one uses it. > > And what about the graphics card etc. ? gentoo has the same what I do, the other guy has a gigabyte clone of same. > > > http://bugs.xfree86.org/show_bug.cgi?id=414 might be related, as the > > > radeon driver doesn't accelerate the RENDER extension yet. > > Note this comment http://bugs.xfree86.org/show_bug.cgi?id=414#c18 - it does > > seem to confirm that the metacity itself might be the cause of the slowness. > > I fail to see how metacity can have an impact on x11perf, it certainly > doesn't here. That's not what I meant by pointing it out, but rather the comment the guy makes about metacity being sluggish. The x11perf is just for comparison with some model system, I presume. And the comparison of sawfish with metacity makes it quite clear that metacity is slow. With sawfish when flipping workspaces I can hardly see the desktop+windows redraw while with metacity I can easily make out the three phases - original workspace is "erased" with the root window redraw, then on the new workspace first the windows frames are drawn (and it's really visible..) and then the window interiors, with a flicker. In fact, when switching to a workspace with maximized mozilla window displaying a largish document I'm pretty much positive that the window interior is redrawn twice. Anyhow, not knowing what's the cause, I know that metacity is really, really slow on a fast system :( thanks, marek
Attachment:
pgp7TpnwATmT2.pgp
Description: PGP signature