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.

Sign up for GitHub

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

Jump to bottom

Optimize running aggregate bloom filter storage #2354

Open
sistemd opened this issue Nov 5, 2024 · 0 comments · Fixed by #2367
Open

Optimize running aggregate bloom filter storage #2354

sistemd opened this issue Nov 5, 2024 · 0 comments · Fixed by #2367
Assignees
@sistemd
Milestone
Aggregate Bloom f...

Comments

@sistemd
Copy link
Contributor

sistemd commented Nov 5, 2024

Currently the running aggregate is read from storage and written back on each block. We can keep it in memory instead and handle some special cases, and then only write it when it's been completed.

#2348 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sistemd sistemd

Labels
None yet
Projects
None yet
Milestone
Aggregate Bloom filters
Development

Successfully merging a pull request may close this issue.

feat(bloom): store running aggregate in memory eqlabs/pathfinder
2 participants
@kkovaacs @sistemd