Repository navigation
perf(files): cache the mimetype table - #65430
Merged
Merged
Conversation
Every request that reads a file cache entry loaded the whole mimetypes table from the database. Keep it in the local cache instead. Mimetypes are only ever added, so a stale cache can only miss new mimetypes: on a miss the table is loaded from the database again, at most once per request. Assisted-by: ClaudeCode:claude-opus-5-5 Signed-off-by: Carl Schwan <carl@carlschwan.eu>
susnux
approved these changes
Oct 12, 2026
come-nc
approved these changes
Oct 12, 2026
5 of 7 tasks
Member
Author
|
/backport to stable35 |
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
Every request that reads a file cache entry loaded the whole mimetypes table from the database. Keep it in the local cache instead. Mimetypes are only ever added, so a stale cache can only miss new mimetypes: on a miss the table is loaded from the database again, at most once per request.
TODO
Checklist
3. to review, feature component)stable32)AI (if applicable)