From: Johnathan Corgan <johnathan@corganlabs•com>
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 12:41:17 -0800 [thread overview]
Message-ID: <CALOxbZubcT63VHFowdJBBTziHfVV1qnBEREMa+3ctnRRBzf-cg@mail.gmail.com> (raw)
In-Reply-To: <5640F172.3010004@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]
On Mon, Nov 9, 2015 at 11:18 AM, Peter Tschipper via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> 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.
>
The trade-off decisions among bandwidth savings, CPU performance, and
latency are local, and I think it shouldn't be assumed that any particular
node will want to support it. I recommend that if P2P message compression
is implemented, it should be negotiated via the services field at
connection time.
--
Johnathan Corgan
Corgan Labs - SDR Training and Development Services
http://corganlabs.com
[-- Attachment #2: Type: text/html, Size: 1942 bytes --]
next prev parent reply other threads:[~2015-11-09 20:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 19:18 Peter Tschipper
2015-11-09 20:41 ` Johnathan Corgan [this message]
2015-11-09 21:04 ` Bob McElrath
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=CALOxbZubcT63VHFowdJBBTziHfVV1qnBEREMa+3ctnRRBzf-cg@mail.gmail.com \
--to=johnathan@corganlabs$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=peter.tschipper@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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