Optimize analytics overview queries#430
Merged
Merged
Conversation
Contributor
|
No code issues remain. See task
Reviewed b2386af |
mrubens
marked this pull request as ready for review
July 16, 2026 16:53
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
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.
Summary
Why
The analytics page built the same row set independently for its chart and filter controls. Cost analytics also transferred complete task-run payloads and multiplied usage rows through its PR-attribution join. These patterns made request cost grow unnecessarily with inference-event volume.
Impact
Tasks and costs now load chart data and filter options from one consistent row snapshot. Cost analytics performs less database work and transfers substantially less JSON while preserving environment and pull-request attribution.
Validation
@roomote/webTypeScript check