Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

txindex: reduce its size down to 20% 🎉 #116

Open
gdassori opened this issue Jun 15, 2021 · 1 comment
Open

txindex: reduce its size down to 20% 🎉 #116

gdassori opened this issue Jun 15, 2021 · 1 comment

Comments

@gdassori
Copy link
Member

gdassori commented Jun 15, 2021

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%!

@gdassori gdassori changed the title txindex: reducing its size down to 20%. txindex: reducing its size down to 20% 🎉 Jun 15, 2021
@gdassori gdassori changed the title txindex: reducing its size down to 20% 🎉 txindex: reduce its size down to 20% 🎉 Jun 15, 2021
@gdassori
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant