Bitcoin full node and query server

Sep 2, 2019

View in context in the libbitcoin Slack #general mirror.

evoskuil22:29

My last work in blockchain was block caching during sync, so that a large memory machine could cache blocks received out of order up to the size of the entire chain, eliminating the block read required for validation purposes. The other remaining optimization to complete is minimizing the scope of confirmation updates.

(edited)

jungly22:37

Yup. Totally get that. It's just a to measure things, so we can know how things are improving etc. I was curious to know how much io was coming due to vm paging effort. I went for a 256 GB ram and 12 virtual cores wth nvme SSD machine. It looked interesting how there were no real page faults up to a certain amount of memory usage and then they go up quiet rapidly (kind of expected). But I'll share the results soon so we can look interpret them properly.