Update docs for SRC.MemoryCache #11375
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
github-actions
bot
added
the
needs-area-label
gewarren
approved these changes
May 30, 2025
Looks fine to me. Co-authored-by: Genevieve Warren <[email protected]>
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.
Update docs for SRC.MemoryCache - memory limits were being presented
This pull request updates the documentation for the
MemoryCacheclass inSystem.Runtime.Cachingto clarify the behavior of memory limit properties (CacheMemoryLimitandPhysicalMemoryLimit) across different .NET versions and their impact on cache eviction.Updates to
MemoryCachedocumentation:Changes to
CacheMemoryLimitproperty:CacheMemoryLimitproperty does not enforce memory limits in .NET Core and .NET 5.0 or later, but remains functional in .NET Framework. Updated remarks to reflect this behavior and removed outdated information about gradual enforcement using internal heuristics.Changes to
PhysicalMemoryLimitproperty:PhysicalMemoryLimitproperty triggers cache eviction based on overall system memory usage rather than limiting the memory usage of a singleMemoryCacheinstance. Revised remarks to emphasize its role in reducing memory pressure when system-wide physical memory usage exceeds the configured threshold.incorrectlySummary
Describe your changes here.
Fixes #Issue_Number (if available)
dotnet/runtime#114714
dotnet/runtime#74676
dotnet/runtime#62516