Type in aspnetcore/performance/caching/memory.md (#5364)
adjust the priority the cache evicts => adjust the priority with which the cache evicts Fixes #5363pull/5359/head
parent
e7b9a172a1
commit
f5e844fadb
|
@ -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[]`.
|
||||
|
||||
|
|
Loading…
Reference in New Issue