Sorry, but I've quantified the reasons why it should be disabled on a LAN. If you see some benefit in performance on a WAN, then you need to quantify that as well. I will not endorse TigerVNC unless it is "performant by default." The CUT uses a significant amount of server CPU time, so if it benefits WAN-based scenarios, it needs to be quantified how much and how much of a CPU time hit is incurred from the LAN-based scenarios. If it benefits only one and not the other, then the default behavior needs to be enabling it only when it shows a clear benefit without compromising overall frame rate.
On Nov 10, 2011, at 8:08 AM, Pierre Ossman <oss...@cendio.se> wrote: > On Thu, 10 Nov 2011 07:33:58 -0600 > DRC <dcomman...@users.sourceforge.net> wrote: > >> 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. >> > > Firefox is hardly something that is almost never used. Compositing is > also something that is very popular in modern desktop systems. I'd like > to see how much it can improve things with Unity 2D for example. > > I'd say that the majority of users will benefit from this feature being > turned on. It should therefore be turned on by default, and the people > who don't need it can turn it off. > > 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
