[Bitcoin-development] Scalability issues

Gregory Maxwell gmaxwell at gmail.com
Fri Jul 27 06:56:06 UTC 2012

On Fri, Jul 27, 2012 at 1:59 AM, grarpamp <grarpamp at gmail.com> wrote:
>> I now have an 1.8 ghz p3 celeron (128k cache) which should be
>> substantially slower than your machine, running vintage 2.6.20 linux.
>> Unfortunately I forgot to turn on timestamp logging so I don't know
>> how long it took to sync the chain, but it was less than two days as
>> that was the span between when I checked on it. It's staying current
> Well, are you running bitcoin on, say, an FS with sha256 integrity
> trees for all bits and AES-128-XTS/CBC disk encryption?
> If not, we're not comparing the same apples, let alone the same OS.

The file system is using twofish-cbc-essiv:sha256, apparently.  (I
went and dug up a mothballed machine of mine because of your post).

And I agree, encrypting everything is a good practice— I once got a
disk back from RMA where only the first sectors were zeroed and the
rest had someone elses data, since then I've encrypted everything
because you can't wipe a dead drive.

I'd love to know precisely what Bitcoin is doing thats making your
machine so unhappy... but your configuration is uncommon for bitcoin
nodes in many distinct ways so it's not clear where to start.

More information about the bitcoin-dev mailing list