You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The txindex is huge.
I estimate that some sort of firstbits implementation would reduce the txindex size down to 20-25%, even less! And this is awesome.
The downside is having a bit more iterations while lurking, maybe, but.. who cares? 20%!
The text was updated successfully, but these errors were encountered:
gdassori
changed the title
txindex: reducing its size down to 20%.
txindex: reducing its size down to 20% 🎉
Jun 15, 2021
gdassori
changed the title
txindex: reducing its size down to 20% 🎉
txindex: reduce its size down to 20% 🎉
Jun 15, 2021
It is very intensive to index the Firstbits, because an iterator must be run at every write operation.
To avoid bottlenecks, the FB compression must be run into a separate task.
Transactions must be indexed on a normal DB and moved to the Firstbits index later.
It sounds good to run the whole Transactions Index process as separated.
It may take up to a while to sync a full node on a low-end VPS and compress the transactions index.
The txindex is huge.
I estimate that some sort of firstbits implementation would reduce the txindex size down to 20-25%, even less! And this is awesome.
The downside is having a bit more iterations while lurking, maybe, but.. who cares? 20%!
The text was updated successfully, but these errors were encountered: