From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42384) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZWKsH-0003w9-35 for qemu-devel@nongnu.org; Mon, 31 Aug 2015 04:55:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZWKsD-00009L-0I for qemu-devel@nongnu.org; Mon, 31 Aug 2015 04:55:33 -0400 Received: from mx-v6.kamp.de ([2a02:248:0:51::16]:33537 helo=mx01.kamp.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZWKsC-00008q-MK for qemu-devel@nongnu.org; Mon, 31 Aug 2015 04:55:28 -0400 References: <1440679585-13984-1-git-send-email-pl@kamp.de> <1440762963.20725.3.camel@redhat.com> From: Peter Lieven Message-ID: <55E4166E.1050902@kamp.de> Date: Mon, 31 Aug 2015 10:55:10 +0200 MIME-Version: 1.0 In-Reply-To: <1440762963.20725.3.camel@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed 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: Gerd Hoffmann Cc: qemu-devel@nongnu.org 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. I understand your concern of twice encoding, but I think there is no easy way to avoid this. However, sending the data as raw later on is a cheap operation because the patch only does it when no pixel conversion has to be made. Peter