From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LSZ7n-0006pS-Pq for qemu-devel@nongnu.org; Thu, 29 Jan 2009 10:48:15 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LSZ7m-0006ox-3j for qemu-devel@nongnu.org; Thu, 29 Jan 2009 10:48:14 -0500 Received: from [199.232.76.173] (port=58176 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LSZ7l-0006op-Su for qemu-devel@nongnu.org; Thu, 29 Jan 2009 10:48:13 -0500 Received: from mail-qy0-f20.google.com ([209.85.221.20]:39819) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LSZ7l-0004Xz-JD for qemu-devel@nongnu.org; Thu, 29 Jan 2009 10:48:13 -0500 Received: by qyk13 with SMTP id 13so12469230qyk.10 for ; Thu, 29 Jan 2009 07:48:12 -0800 (PST) Message-ID: <4981CFAD.9000609@codemonkey.ws> Date: Thu, 29 Jan 2009 09:47:57 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH 7/7] Add tight encoding (jpeg) to vnc.c References: <1233228298-4844-1-git-send-email-agraf@suse.de> <1233228298-4844-2-git-send-email-agraf@suse.de> <1233228298-4844-3-git-send-email-agraf@suse.de> <1233228298-4844-4-git-send-email-agraf@suse.de> <1233228298-4844-5-git-send-email-agraf@suse.de> <1233228298-4844-6-git-send-email-agraf@suse.de> <1233228298-4844-7-git-send-email-agraf@suse.de> <1233228298-4844-8-git-send-email-agraf@suse.de> <4981C8A2.8070405@codemonkey.ws> <4981C9E0.6050708@eu.citrix.com> In-Reply-To: <4981C9E0.6050708@eu.citrix.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Alexander Graf Stefano Stabellini wrote: > Anthony Liguori wrote: > > >> If we implement Tight and then use jpeg by default, for most clients, >> the default is going to be lossy encoding. While lossy isn't so bad for >> high detailed images (like pictures), it's pretty terrible for simple, >> high contrast images (like windows in a desktop). >> >> TightVNC has some sophisticated heuristics for determining whether to >> use jpeg or not (when it's enabled). I think that sort of heuristic is >> a prerequisite for enabling tight's jpeg support. >> >> FWIW, Tight essentially does hextile encoding but adds zlib >> compression. That's probably a better place to start as it should >> outperform hextile while remaining lossless. >> >> > > Another thing to consider is that using jpeg compression is going to > worsen qemu performances, so I think it should be used only when > necessary, e.g. the network connection between client and server is bad. > Most clients I know do not enable JPEG by default. It requires a user to explicitly do so. Regards, Anthony Liguori