RFC: PostgreSQL trace query optimization#1
Open
aws-khatria wants to merge 2 commits into
Open
Conversation
Proposes composite indexes, token metric denormalization, and experiment_id addition to assessments table to improve Usage page and Traces page load times at scale.
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.
Proposes schema-level optimizations to improve MLflow trace analytics performance on PostgreSQL — based on a load test with 10M traces, 30M spans, and 30M assessments.
Happy for suggestions to further improve the MLflow dashboarding experience.