Add caching and pagination; display builds in increasing order#2
Merged
Conversation
Owner
|
Thanks |
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
2 participants
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.
The problem
Previously the viewer rescanned the entire screenshot directory on
every request. For targets containing many builds and movies this
resulted in very slow page loads and heavy filesystem usage.
What changes after this PR
Introduce a cache storing computed timeline ranges so subsequent
requests reuse the results instead of reprocessing all screenshots.
Add pagination to the builds list to avoid extremely long pages
when many builds are present.
Finally, display builds in chronological (increasing) order so the
timeline reflects build progression and is easier to read.