From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46256) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZXQI3-0004HC-Q3 for qemu-devel@nongnu.org; Thu, 03 Sep 2015 04:54:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZXQHz-0006eq-P5 for qemu-devel@nongnu.org; Thu, 03 Sep 2015 04:54:39 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47513) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZXQHz-0006ed-K7 for qemu-devel@nongnu.org; Thu, 03 Sep 2015 04:54:35 -0400 Message-ID: <1441270471.557.11.camel@redhat.com> From: Gerd Hoffmann Date: Thu, 03 Sep 2015 10:54:31 +0200 In-Reply-To: <55E4166E.1050902@kamp.de> References: <1440679585-13984-1-git-send-email-pl@kamp.de> <1440762963.20725.3.camel@redhat.com> <55E4166E.1050902@kamp.de> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] vnc: allow fall back to RAW encoding List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Lieven Cc: qemu-devel@nongnu.org On Mo, 2015-08-31 at 10:55 +0200, Peter Lieven wrote: > Am 28.08.2015 um 13:56 schrieb Gerd Hoffmann: > > On Do, 2015-08-27 at 14:46 +0200, Peter Lieven wrote: > >> I have observed that depending on the contents and the encoding it happens > >> that sending data as RAW sometimes would take less space than the encoded data. > >> This is especially the case for small updates or areas with high color images. > >> If sending RAW encoded data is beneficial allow a fall back to RAW encoding > >> for the framebuffer update. > > Do you happen to have some stats for this, especially the "small update" > > case? We might want to go straight to raw (without trying other > > encodings) for small updates, to avoid encoding things twice. > > I had a look at hextile, zrle, tight and zlib encoding. It seems that the case > that raw encoding is smaller never happens for zrle and tight. For zlib and > hextile its quite common, but there is no obvious mark for the size of the > update. It seems to heavily depend on the contents as assumed earlier. Ok, taking patch as-is then. cheers, Gerd