Skip to content

[DB] Optimisations #45

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
Open
frisitano opened this issue Apr 2, 2025 · 0 comments
Open

[DB] Optimisations #45

frisitano opened this issue Apr 2, 2025 · 0 comments
Assignees
@greged93
Labels
database enhancement New feature or request milestone 5 This issue is part to Milestone 5 of the Rollup Node plan
Milestone
Milestone 5

Comments

@frisitano
Copy link
Collaborator

frisitano commented Apr 2, 2025 •
edited
Loading

Overview

We should consider the database access patterns and introduce indexes or other optimisations to make the database more efficient. One low hanging fruit would be to introduce an index on the batch hash. Given that our dataset of medium size (~360k batches / ~1m L1 messages) it could benefit from indexes but even without them it should be pretty fast, and as such, this is of low/medium priority.
@frisitano frisitano added this to the Milestone 5 milestone Apr 10, 2025
@frisitano frisitano added the milestone 5 This issue is part to Milestone 5 of the Rollup Node plan label Apr 10, 2025
@greged93 greged93 changed the title Database Optimisations [DB] Optimisations Apr 24, 2025
@frisitano frisitano added this to Reth Apr 25, 2025
@frisitano frisitano added the enhancement New feature or request label Apr 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@greged93 greged93

Labels
database enhancement New feature or request milestone 5 This issue is part to Milestone 5 of the Rollup Node plan
Projects
Reth
Status: No status
Milestone
Milestone 5
Development

No branches or pull requests
2 participants
@frisitano @greged93