For testnet you might vary these recommendations a bit. Block polling can stay lower, between 1-5 seconds. Cache could increase some, say 10000.



I haven’t tried varying store hash table bucket sizing, waiting for someone to sign up for that testing 😊.



e



From: Eric Voskuil [mailto:eric@voskuil.org]
Sent: Thursday, March 9, 2017 1:03 AM
To: 'Lucas Betschart' <lucasbetschart@???>
Cc: 'Libbitcoin Development' <libbitcoin@???>
Subject: RE: [Libbitcoin] version3 signed binaries



Yes, there are lots of ways to speed up config. Also note that the current sync is blocks first, so it is generally suboptimal for initial block download. I disabled the extremely fast parallel initial block download for the release but I’ll be bringing it back.



I’ll be writing up config recommendations next. There is still a lot of manual config to get things optimal, which we’ll be working out in v4.



Disabling write flushing is the most significant factor. Then take the connections down to 3 and set connection lifetime to 30-60 minutes. Disable server services and transaction relay. Set block poling to 1 second until 200k and then 10 seconds until 300k and then 15 seconds (reduces redundant blocks). A high checkpoint of course will reduce validation time. With 16MB RAM I recommend cache_capacity of about 5000 (txs). Finally, rotate your logs off of the SSD and use a rotation size of about 10000000. Otherwise defaults are optimal.



Also node syncs much faster than server (and is the proper comparison to other nodes that don’t index the entire blockchain of addresses like bs does). BS can be set to start indexing addresses at any height, which makes a big difference. It’s basically the same as node if you set height above the top block, though that’s not to useful if you want to run queries against it.



Don’t run out of disk space. You can reduce the expansion rate once it gets larger. When fully synced I set it to 10%.



e



From: Lucas Betschart [mailto:lucasbetschart@gmail.com]
Sent: Thursday, March 9, 2017 12:53 AM
To: Eric Voskuil <eric@??? <mailto:eric@voskuil.org> >
Cc: Libbitcoin Development <libbitcoin@??? <mailto:libbitcoin@lists.dyne.org> >
Subject: Re: [Libbitcoin] version3 signed binaries



Very nice. Syncing a fresh testnet bs on my notebook right now :)
I've made all the necessary changes for testnet according to the documentation (and it seems to be working with bx), but is there a way to speed up the sync with some config?

E.g. would it help if I set flush_writes to false so it writes in batches?

I'm using a MacBook Pro (2016)
2.9 GHz Intel Core i7
16 GB 2133 MHz LPDDR3



bs uses 98% of the CPU, but only 80 MB of memory it seems.


Best regards

Lucas



2017-03-09 8:45 GMT+01:00 Eric Voskuil <eric@??? <mailto:eric@voskuil.org> >:

Signed version3 binaries are now available:

https://github.com/libbitcoin/libbitcoin-node/wiki/Download-BN
https://github.com/libbitcoin/libbitcoin-node/releases/tag/v3.0.0

https://github.com/libbitcoin/libbitcoin-server/wiki/Download-BS
https://github.com/libbitcoin/libbitcoin-server/releases/tag/v3.0.0

https://github.com/libbitcoin/libbitcoin-explorer/wiki/Download-BX
https://github.com/libbitcoin/libbitcoin-explorer/releases/tag/v3.0.0

Version3 does not have distinct builds for testnet, so these binaries
are now usable for both testnet and mainnet (and altcoins in the case of
most bx commands).

All other existing readme.MD and wiki documentation has been updated, as
has the libbitcoin section of the bitcoin.it <http://bitcoin.it> wiki:

https://en.bitcoin.it/wiki/Libbitcoin

The libbitcoin.org <http://libbitcoin.org> website is presently offline, which is being resolved.

I'll be working on FAQs and detailed node/server configuration
documentation over the next few days.

e


_______________________________________________
Libbitcoin mailing list
Libbitcoin@??? <mailto:Libbitcoin@lists.dyne.org>
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/libbitcoin







--

Best regards



Lucas