Not sure if I understand why it couldn't be overridden by passing compareFB=1 on the command prompt to always enable it.
On 11/17/11 7:23 AM, Pierre Ossman wrote: > Suggested patch. It does the following: > > - CUT block size changed to 64 pixels. This size in most cases has a > CPU usage similar to 256 pixels, but a coverage more similar to 16 > pixels. > > - Default compression level changed to 2. Based on your numbers, this > seems to get us most of the compression, whilst avoiding most of the > CPU usage (compared to level 3). > > - CUT enabled by default. Will be disabled if all clients advertise a > compression level of 1 or below. compareFB=0 will forcefully disable > it at all times. There is currently no way to enable it as well as > have a low compression setting. > > Does this seem ok to you? > > Rgds ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
