From f5e844fadb5879346d2eb0ed47a57b2d9322639b Mon Sep 17 00:00:00 2001 From: Antoine Griffard Date: Sat, 3 Feb 2018 20:20:55 +0100 Subject: [PATCH] Type in aspnetcore/performance/caching/memory.md (#5364) adjust the priority the cache evicts => adjust the priority with which the cache evicts Fixes #5363 --- aspnetcore/performance/caching/memory.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/performance/caching/memory.md b/aspnetcore/performance/caching/memory.md index 603a8e34c8..171bf5d978 100644 --- a/aspnetcore/performance/caching/memory.md +++ b/aspnetcore/performance/caching/memory.md @@ -25,7 +25,7 @@ ASP.NET Core supports several different caches. The simplest cache is based on t Non-sticky sessions in a web farm require a [distributed cache](distributed.md) to avoid cache consistency problems. For some apps, a distributed cache can support higher scale out than an in-memory cache. Using a distributed cache offloads the cache memory to an external process. -The `IMemoryCache` cache will evict cache entries under memory pressure unless the [cache priority](https://docs.microsoft.com/aspnet/core/api/microsoft.extensions.caching.memory.cacheitempriority) is set to `CacheItemPriority.NeverRemove`. You can set the `CacheItemPriority` to adjust the priority the cache evicts items under memory pressure. +The `IMemoryCache` cache will evict cache entries under memory pressure unless the [cache priority](https://docs.microsoft.com/aspnet/core/api/microsoft.extensions.caching.memory.cacheitempriority) is set to `CacheItemPriority.NeverRemove`. You can set the `CacheItemPriority` to adjust the priority with which the cache evicts items under memory pressure. The in-memory cache can store any object; the distributed cache interface is limited to `byte[]`.