Repository navigation
⚡ [Performance] Cache deserialized AppSettings in SettingsService - #68
Merged
Merged
Conversation
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
1 participant
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.
💡 What: Caches the deserialized AppSettings instance in SettingsService after loading from disk, and invalidates/updates it on SaveSettings.
🎯 Why: SettingsService.LoadSettings() was repeatedly hitting disk and deserializing JSON on every call throughout the application lifecycle.
📊 Result: Repeated calls to LoadSettings() return the cached instance immediately without disk I/O, reducing execution time and allocation overhead significantly.
Addresses Jules session 9324059400750656685.