"Fixed a bug that caused extremely slow rendering of OpenGL applications on X screens other than screen 0 when using a compositing manager."Well that sounds nice. Hands up who runs compiz on an nvidia card with two screens using xinerama? You might notice your GL screensavers run incredibly slow. Here's some examples, for testing I used glmatrix which you might be able to run directly via /usr/lib/misc/xscreensaver/glmatrix.
I have a Core(TM)2 Duo CPU T9500 @ 2.60GHz laptop with an nVidia Quadro FX 1600M, 1920x1200 screen and a second 1920x1200 LCD. I've loaded the new 256.53 nvidia module. Here are the results:
|Compositing manager||screen 0||screen 1||Performance|
|none (gnome + metacity)||glmatrix @ 1920x1200||nothing||FPS: 29|
|none (gnome + metacity)||glmatrix @ 1920x1200||glmatrix @ 1920x1200||FPS: 29 (both)|
|compiz & emerald||glmatrix @ 1920x1200||nothing||FPS: 29|
|compiz & emerald||glmatrix @ 1920x1200||glmatrix @ 1920x1200||FPS: 4 (both)|
|compiz & emerald||nothing||glmatrix @ 1920x1200||FPS: 5|
As you can see, there is little difference between one or two full screen gl effects running without a compositing manager.
However, any effects on the second screen while running compiz is enough to drastically degrade performance.
As a second test, I ran six glmatrix hacks at their default resolution (about 640x480) on screen 0 with and without compiz. The results were the same:
FPS: 14 - 20
Load: 45 - 70%