From: Marco Pontello <marcopon@gmail.com>
To: Jeff Johnson <jjxtra@gmail.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Block compression
Date: Mon, 27 Nov 2017 13:08:05 +0100 [thread overview]
Message-ID: <CAE0pACLYZihmVU6GMpONmcOKfAVa-DojuQsAXAiOpcN9CamcHA@mail.gmail.com> (raw)
In-Reply-To: <CAHAcUENRbrz6pv_HSe4KDAY-onyMKnMJk8H6yUhqx4LoK0NeEw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 420 bytes --]
Hi Jeff!
On Mon, Nov 27, 2017 at 3:11 AM, Jeff Johnson via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Raw block
> 998,198 bytes
>
> Gzip
> 521,212 bytes (52% ratio)
> (needs 2MB to decompress).
>
I don't know how you got that raw block, but it seems a bit odd.
If you look at it in an hex editor, you'll notice that every odd byte is 0,
and that explain the unusual high compression ratio.
Bye!
[-- Attachment #2: Type: text/html, Size: 914 bytes --]
next prev parent reply other threads:[~2017-11-27 12:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 2:11 [bitcoin-dev] Block compression Jeff Johnson
2017-11-27 2:32 ` [bitcoin-dev] 答复: " lonsdale aseaday
2017-11-27 12:08 ` Marco Pontello [this message]
2017-11-27 20:49 ` [bitcoin-dev] " Jonas Schnelli
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=CAE0pACLYZihmVU6GMpONmcOKfAVa-DojuQsAXAiOpcN9CamcHA@mail.gmail.com \
--to=marcopon@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=jjxtra@gmail.com \
/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