Strongly object. The performance hit by turning it on is severe and not something that can just be optimized away. My testing shows that the CUT is almost never used.
On Nov 10, 2011, at 6:34 AM, Pierre Ossman <oss...@cendio.se> wrote: > I've done some tests of the CUT and I've determined that it does > provide a very substantial benefit, and does so for common cases. What > I've tested with so far are: > > a) firefox (probably all double buffered applications) > b) metacity with compositing > > In both cases it removes upwards 90% of the changes, which is a massive > saving. And the cases above aren't rare and exotic. > > (I also seem to recall that Qt4 does double buffering by default) > > So I say we need to turn it back on by default. If it has performance > issues, then we should look at optimising it, not killing it completely. > > Rgds > -- > Pierre Ossman OpenSource-based Thin Client Technology > System Developer Telephone: +46-13-21 46 00 > Cendio AB Web: http://www.cendio.com > > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > ------------------------------------------------------------------------------ > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > _______________________________________________ > Tigervnc-devel mailing list > Tigervnc-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tigervnc-devel ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
