j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMµ<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1931.msg25138#msg25138">Quote from: satoshi on November 28, 2010, 05:13:01 PM</a></div><div class="quote">If there was a "verify it" step, that would take as long as the current initial download, in which it is the indexing, not the data download, that is the bottleneck.<br/>[...]<br/>The speed of initial download is not a reflection of the bulk data transfer rate of the protocol. The gating factor is the indexing while it downloads.<br/></div><br/>Sorry, these users' disk and CPU were <i>not</i> at 100%. It is clear the bottleneck is <i>not</i> the database or indexing, for many users.<br/><br/><div class="quoteheader">Quote</div><div class="quote">The data is mostly hashes and keys and signatures that are uncompressible.<br/></div><br/>bzip2 gives you 33% compression ratio, saving many megabytes off a download:<br/><br/><div class="codeheader">Code:</div><div class="code">[jgarzik@bd data]$ tar cvf /tmp/1.tar blk0001.dat <br/>blk0001.dat<br/><br/>[jgarzik@bd data]$ tar cvf /tmp/2.tar blk*.dat<br/>blk0001.dat<br/>blkindex.dat<br/><br/>[jgarzik@bd data]$ bzip2 -9v /tmp/[12].tar<br/> /tmp/1.tar: 1.523:1, 5.253 bits/byte, 34.34% saved, 55439360 in, 36402074 out.<br/> /tmp/2.tar: 1.512:1, 5.291 bits/byte, 33.86% saved, 103690240 in, 68577642 out.<br/></div><br/>I wouldn't call 33% "uncompressible"</div> text/html
https://whatsonchain.com/tx/ea7b4cbb83d5df3b631f8b94e0b3386ec0ccf665b08ea2bd4cd3a0d767c0efb8