Performance

Charts below present system memory and time needed to sync BTC block chain up to the given block number.

Note:
Gocoin uses (configurable) LastTrustedBlock to avoid verifying scripts from all blocks known as valid.
Referenced Bitcoin Core uses an identical mechanism (configurable with assumevalid parameter).
Both implementations come with a recent trusted block built into their code (no need to configure them explicitly).

Gocoin 1.10.1, built with Go 1.18.3

Dedicated server with 3.4GHz Intel i7-6700 CPU and HDD

With comparision to Bitcoin Core 23.0:

Both the clients were using their default configuration.

Dedicated server with 3.6GHz Intel i7-7700 CPU and SSD

Default config:


Time needed to re-build UTXO database from blocks stored on the disk: 1.2 hours (up to block #700000)

Tweaked config:


Changed config values:

Dedicated server with 3.4GHz Intel i7-6700 CPU and SSD

Default config:


Time needed to re-build UTXO database from blocks stored on the disk: 1.3 hours (up to block #700000)

Dedicated server with 3.4GHz Intel i7-4770 CPU and HDD

Default config:


Time needed to re-build UTXO database from blocks stored on the disk: 1.4 hours (up to block #700000)

Tweaked config:


Time needed to re-build UTXO database from blocks stored on the disk: 1.3 hours (up to block #700000)
Changed config values:

Gocoin 1.10.0, built with Go 1.17.3

Dedicated server with 3.5GHz Xeon E3-1270 v3 CPU and SSD

Default config:


Time needed to re-build UTXO database from blocks stored on the disk: 1.6 hours (up to block #700000)

Dedicated server with two 1.7GHz Xeon E5-2650L v2 CPUs and HDD

Default config:


Time needed to re-build UTXO database from blocks stored on the disk: 2.6 hours (up to block #700000)