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 claimable_balances_current #124

Open
sydneynotthecity opened this issue Jan 2, 2025 · 0 comments
Open

Optimize claimable_balances_current #124

sydneynotthecity opened this issue Jan 2, 2025 · 0 comments
Labels
data-curation-scrum good first issue Good for newcomers

Comments

@sydneynotthecity
Copy link
Contributor

Currently claimable_balances_current is disabled because it has performance issues that require an increase in bq slot reservations to complete in a timely manner. We should optimize claimable_balances_current to finish around the same time as other *_current tables (5-15 mins) without the need for more slot reservations.

Some ideas that may help with performance:

  • Update dbt model to include clustering
  • Run BQ EXPLAIN on claimable_balances_current to see if there is weird shuffling or skew and try to optimize the query and optimize from there
  • Add new field farmfingerprint(balance_id) to integer
  • Make claimants JSON
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
data-curation-scrum good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sydneynotthecity