From: Bob McElrath <bob_bitcoin@mcelrath.org>
To: Peter Tschipper <peter.tschipper@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] request BIP number for: "Support for Datastream Compression"
Date: Mon, 9 Nov 2015 21:04:49 +0000 [thread overview]
Message-ID: <20151109210449.GE5886@mcelrath.org> (raw)
In-Reply-To: <5640F172.3010004@gmail.com>
I would expect that since a block contains mostly hashes and crypto signatures,
it would be almost totally incompressible. I just calculated compression ratios:
zlib -15% (file is LARGER)
gzip 28%
bzip2 25%
So zlib compression is right out. How much is ~25% bandwidth savings worth to
people? This seems not worth it to me. :-/
Peter Tschipper via bitcoin-dev [bitcoin-dev@lists.linuxfoundation.org] wrote:
> This is my first time through this process so please bear with me.
>
> I opened a PR #6973 this morning for Zlib Block Compression for block
> relay and at the request of @sipa this should have a BIP associated
> with it. The idea is simple, to compress the datastream before
> sending, initially for blocks only but it could theoretically be done
> for transactions as well. Initial results show an average of 20% block
> compression and taking 90 milliseconds for a full block (on a very slow
> laptop) to compress. The savings will be mostly in terms of less
> bandwidth used, but I would expect there to be a small performance gain
> during the transmission of the blocks particularly where network latency
> is higher.
>
> I think the BIP title, if accepted should be the more generic, "Support
> for Datastream Compression" rather than the PR title of "Zlib
> Compression for block relay" since it could also be used for
> transactions as well at a later time.
>
> Thanks for your time...
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
> !DSPAM:5640ff47206804314022622!
--
Cheers, Bob McElrath
"For every complex problem, there is a solution that is simple, neat, and wrong."
-- H. L. Mencken
next prev parent reply other threads:[~2015-11-09 21:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 19:18 [bitcoin-dev] request BIP number for: "Support for Datastream Compression" Peter Tschipper
2015-11-09 20:41 ` Johnathan Corgan
2015-11-09 21:04 ` Bob McElrath [this message]
2015-11-10 1:58 ` gladoscc
2015-11-10 5:40 ` Johnathan Corgan
2015-11-10 9:44 ` Tier Nolan
[not found] ` <5642172C.701@gmail.com>
2015-11-10 16:17 ` Peter Tschipper
2015-11-10 16:21 ` Jonathan Toomim
2015-11-10 16:30 ` Tier Nolan
2015-11-10 16:46 ` Jeff Garzik
2015-11-10 17:09 ` Peter Tschipper
2015-11-11 18:35 ` Peter Tschipper
2015-11-11 18:49 ` Marco Pontello
2015-11-11 19:05 ` Jonathan Toomim
2015-11-13 21:58 ` [bitcoin-dev] Block Compression (Datastream Compression) test results using the PR#6973 compression prototype Peter Tschipper
2015-11-18 14:00 ` [bitcoin-dev] More findings: " Peter Tschipper
2015-11-11 19:11 ` [bitcoin-dev] request BIP number for: "Support for Datastream Compression" Peter Tschipper
2015-11-28 14:48 ` [bitcoin-dev] further test results for : "Datastream Compression of Blocks and Tx's" Peter Tschipper
2015-11-29 0:30 ` Jonathan Toomim
2015-11-29 5:15 ` Peter Tschipper
[not found] ` <56421F1E.4050302@gmail.com>
2015-11-10 16:46 ` [bitcoin-dev] request BIP number for: "Support for Datastream Compression" Peter Tschipper
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=20151109210449.GE5886@mcelrath.org \
--to=bob_bitcoin@mcelrath.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=peter.tschipper@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