Skip to content

Add important notes on HybridCache limitations and behavior #34224

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tdykstra merged 3 commits into from
Dec 1, 2024
Merged

Add important notes on HybridCache limitations and behavior #34224

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
559e2ff
Add important notes on HybridCache limitations and behavior
Nov 27, 2024
300f015
Update aspnetcore/performance/caching/hybrid.md based on PR suggestions
Dec 1, 2024
08192e0
Update aspnetcore/performance/caching/hybrid.md
Dec 1, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions aspnetcore/performance/caching/hybrid.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,6 +73,9 @@ When an entry is removed, it is removed from both the primary and secondary cach

## Remove cache entries by tag

> [!IMPORTANT]
> This feature is still under development. If you try to remove entries by tag, you will notice that it won't cause any effect yet.

Tags can be used to group cache entries and invalidate them together.

Set tags when calling `GetOrCreateAsync`, as shown in the following example:
Expand Down Expand Up @@ -145,6 +148,8 @@ For more information, see the [HybridCache serialization sample app](https://git

By default `HybridCache` uses <xref:System.Runtime.Caching.MemoryCache> for its primary cache storage. Cache entries are stored in-process, so each server has a separate cache that is lost whenever the server process is restarted. For secondary out-of-process storage, such as Redis or SQL Server, `HybridCache` uses [the configured `IDistributedCache` implementation](xref:performance/caching/distributed), if any. But even without an `IDistributedCache`implementation, the `HybridCache` service still provides in-process caching and [stampede protection](https://en.wikipedia.org/wiki/Cache_stampede).

**Note:** When invalidating the cache by key or by tags, it will be invalidated in the current node and in the secondary out-of-process storage. However, the in-memory cache on other nodes will not be affected.

## Optimize performance

To optimize performance, configure `HybridCache` to reuse objects and avoid `byte[]` allocations.
Expand Down