Bitcoin full node and query server

Oct 15, 2024

View in context in the libbitcoin Slack #general mirror.

evoskuil12:37

It is likely that the default settings will be suboptimal for your machine, even resulting in thrashing. If you post your basic specs I can make suggestions. One of the aspects we are working on is automatically tuning what is presently manual configuration for given platform. Also note that if your CPU supports sha native (shani), which is about 5x faster individual hashing, it will distort realistic benchmarking, since shani is not yet integrated into the hashing library.

cguida17:47

ok so i am not synced to 524493 here? the block_archived event would show a much lower number?

2024-10-15T17:44:33Z.0 Body sizes...
   header    :84847420
   txs       :189308
   tx        :655464
   point     :28296
   input     :162756
   output    :856072
   puts      :98121
   candidate :2597370
   confirmed :3
   spend     :270960
   strong_tx :126840
   valid_tx  :0
   valid_bk  :0
   address   :0
   neutrino  :0
2024-10-15T17:44:33Z.0 Table records...
   header    :865790
   tx        :10572
   point     :786
   candidate :865790
   confirmed :1
   spend     :11290
   strong_tx :10571
   address   :0
2024-10-15T17:44:33Z.0 Head buckets...
   header    :524493
   txs       :524493
   tx        :551320125
   point     :546188501
   spend     :1459791875
   strong_tx :551320125
   valid_tx  :551320125
   valid_bk  :524493
   address   :1
   neutrino  :1
2024-10-15T17:44:33Z.0 Collision rates...
   header    :1.65072
   txs       :1.65072
   tx        :1.91758e-05
   point     :1.43906e-06
   spend     :7.73398e-06
   strong_tx :1.91758e-05
   valid_tx  :1.91758e-05
   valid_bk  :1.65072
   address   :0
   neutrino  :0