> 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.
That's why I posted the details of the machine so interested people
could duplicate it if they
> You are however using a filesystem (ZFS)
I'm aware of the memory and i386 issues, and going shopping.
> The bdb backend Bitcoin uses
> does many I/O operations, and writes them synchronously to disk, killing
> whatever caching your filesystem provides.
Sync... yes, depending on the rate/sec an
And now to the list...
On Jul 27, 2012 6:21 AM, "grarpamp" wrote:
>
> Update: this class of machine just became useless for bitcoin.
> When blk0002.dat was created to store more blocks, all forward
> progress processing blocks turned into losing ground by 20 or so
> a day. Guessing both datfiles
I propose a pragmatic solution: Try running the Multibit client. i am
not sure if the linux/java based installer would work,so maybe you have
to build it from source.
I tried it out is really fast compared to bitcoin-qt. after install it
took me 15 seconds to get updated and running. Importing a
4 matches
Mail list logo
