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

Mempool - Optimise Angor indexing #176

Closed
nostrdev-com opened this issue Nov 19, 2024 · 0 comments
Closed

Mempool - Optimise Angor indexing #176

nostrdev-com opened this issue Nov 19, 2024 · 0 comments

Comments

@nostrdev-com
Copy link

The current implementation of the indexing process means that it will run each time indexing starts, fetch all the transaction ids and then check if each of these transactions has been indexed by querying a separate database, Angor Blocks Repository.

A possible solution that would eliminate regular, redundant querying is to store two flags, one with the latest block that was indexed and one to verify that all of the blocks up until the latest verify blocks have been indexed. The second flag is needed because in my experience blocks are not always indexed in the consecutive order.

@dangershony dangershony changed the title Optimise Angor indexing mempool - Optimise Angor indexing Nov 19, 2024
@dangershony dangershony changed the title mempool - Optimise Angor indexing Mempool - Optimise Angor indexing Nov 19, 2024
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