feat(Tech: Assets): Split assets over subfolders #1526
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.
Migration required - This moves asset files on disk, so downgrading is less trivial.
Currently all assets are stored on disk in 1 flat directory. This makes that one inode quite heavy. This PR changes this behaviour and instead stores hashes in subfolders based on the start.
This requires a one-time move of all files as well as a patch to some DB meta data.
I should have done this in a separate PR, but while upgrading related code I stumbled upon .paa file handling code that is no longer reachable as the frontend never got updated to support this special custom format. I've removed the code from the server for now as it's quite unmaintained and simply not able to be triggered.