Address subscriptions are slow for addresses with large histories #18
Labels
No labels
area: database
area: documentation
area: elasticsearch
area: herald
area: packaging
area: scribe
consider soon
critical
dependencies
good first issue
hacktoberfest
help wanted
improvement
needs: repro
new feature
priority: blocker
priority: high
priority: low
priority: medium
type: bug
type: bug-fix
type: discussion
type: feature request
type: improvement
type: new feature
type: refactor
type: task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/hub#18
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When a client subscribes to an address the hub needs to send it the hash of the address history to minimally allow the client to check that it has the same history. Currently this is an expensive call that the hub must do, where it has to concatenate the history and then hash it. As the address history grows the heaviness of recalculating the status hash grows with it.
This can be fixed by moving the calculation of address statuses into two new indexes maintained by the block processor: one for address statuses at the new block and another for address statuses factoring in mempool.