Improve expansion run page performance#1836
Merged
AaronPlave merged 2 commits intoJan 13, 2026
Merged
Conversation
… sequences for all expansion runs upfront.
df30d5b to
c7ac752
Compare
duranb
reviewed
Jan 13, 2026
duranb
approved these changes
Jan 13, 2026
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.
Dynamically fetch expansion run details on run row click in the top table instead of fetching all of the nested data for all expansion runs up front. This should significantly improve page load times in scenarios like #1811. Closes #1811.
Verification
OR run this branch on deployment with a large number of expansion runs already in the database, and verify that the Expansion Runs page no longer loads slowly.