added indexes to speed historical queries#320
Open
nanaabdul1172 wants to merge 1 commit into
Open
Conversation
|
@nanaabdul1172 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #113
This change adds targeted indexes to speed up recent time-range and symbol-based historical queries: the schema at schema.prisma was updated to add
@@index([updatedAt])onPriceHistory,MultiSigPrice,Relayer,OhlcCandle,ComplianceMetadata, andPendingConsensus, and@@index([symbol])plus@@index([updatedAt])onCurrency; these indexes optimize 7‑day chart and other recent-data lookups by enabling efficient filtering/sorting onupdatedAtand quick symbol-based scans. Apply the DB changes locally withnpx prisma migrate dev --name add-updatedAt-symbol-indexes(ornpx prisma db pushfor a non-migration push), and create/run a proper migration in your production deployment pipeline.