qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Lieven <pl@kamp.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] vnc: allow fall back to RAW encoding
Date: Mon, 31 Aug 2015 10:55:10 +0200	[thread overview]
Message-ID: <55E4166E.1050902@kamp.de> (raw)
In-Reply-To: <1440762963.20725.3.camel@redhat.com>

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

  parent reply	other threads:[~2015-08-31  8:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27 12:46 [Qemu-devel] [PATCH] vnc: allow fall back to RAW encoding Peter Lieven
2015-08-28 11:56 ` Gerd Hoffmann
2015-08-28 18:24   ` Peter Lieven
2015-08-31  8:55   ` Peter Lieven [this message]
2015-09-03  8:54     ` Gerd Hoffmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55E4166E.1050902@kamp.de \
    --to=pl@kamp.de \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).