Asset load boast using metadata files #67
Merged
Conversation
This file contains 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.
Loading old livesim content took over a minute because every segment is read and scanned at startup time.
The only metadata extracted is startTime, endTime and number of each segment.
This PR makes it possible to generate gzipped JSON files with such metadata for each representation, and read such
files on startup to improve startup speed. The time went from 90s to 4s in tests.
The writing is not on by default, and the directory where the the metadata is read can be configured.
By default, it is the same root as vodRoot, leading to that the metadata files are in the same directories as the MPDs.
A possible extension would be in place if BaseURL is supported in the assets.
Solves #66