Bitcoin slices integration#913
Conversation
|
Good idea, thanks! |
4ce50a7 to
d7c06e7
Compare
|
these are profiles while running before: https://share.firefox.dev/3KCBdPV after: https://share.firefox.dev/3KkfHPE About 3 seconds are shaved off, but most of the time only the main thread is doing something, not sure what. The section finding inputs and outputs looks much faster |
d7c06e7 to
7fdbbf4
Compare
found out, is getting blocks, for creating merkle proofs |
antonilol
left a comment
There was a problem hiding this comment.
always in for performance improvements! here are a few things i found while reading through the code
|
needs some squashing, will do it after @romanz review (or before if asked) |
e80a963 to
e3ad9a1
Compare
|
Will review this weekend, thanks @RCasatta and @antonilol! P.S. |
8bdaae6 to
d0a33bc
Compare
Fixed |
romanz
left a comment
There was a problem hiding this comment.
LGTM, with a few suggested changes:
RCasatta/electrs@poc_bitcoin_slices...romanz:electrs:poc_bitcoin_slices
WDYT?
|
Sorry, for taking some time but I was AFK. utACK a716847 |
a716847 to
84f1c3e
Compare
Co-authored-by: Roman Zeyde <me@romanzey.de>
84f1c3e to
2ea0208
Compare
|
Squashed and rebased over latest master (due to #922) |
This is a proof of concept using bitcoin_slices since it seems a good fit.
Parsing a block with rust_bitcoin is expensive because of allocating all the needed data, since many times you are interested only in a subset of it, we can skip most of the work, for example, to find a transaction.
UPDATED: added visiting of inputs and outputs via bitcoin_slices since the idea seems interesting for the maintainer
Fixes #864.