Skip to content

RS: Added explanation of temporarily exceeding DB memory limits due to adaptive memory allocation #1834

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
merged 7 commits into from
Aug 27, 2025
Merged

RS: Added explanation of temporarily exceeding DB memory limits due to adaptive memory allocation #1834

Changes from 2 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
2ccfef1
DOC-5275 RS: Added explanation of temporarily exceeding DB memory lim…
rrelledge Jun 30, 2025
1b42e9a
Merge branch 'main' into DOC-5275
rrelledge Jul 9, 2025
dc3281a
Fixed outdated relref
rrelledge Jul 9, 2025
cbffca8
Merge branch 'main' into DOC-5275
rrelledge Jul 30, 2025
146ab8b
DOC-5275 Feedback updates for adaptive memory allocation section
rrelledge Jul 30, 2025
99fbf57
Merge branch 'main' into DOC-5275
rrelledge Aug 1, 2025
3f2cda4
DOC-5275 Added an example of a DB temporarily exceeding its memory limit
rrelledge Aug 1, 2025
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
6 changes: 6 additions & 0 deletions content/operate/rs/databases/memory-performance/memory-limit.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,12 @@ but tries to avoid stopping primary shards.
We recommend that you have a [monitoring platform]({{< relref "/operate/rs/monitoring/" >}}) that alerts you before a system gets low on RAM.
You must maintain sufficient free memory to make sure that you have a healthy Redis Enterprise installation.

## Adaptive memory allocation

During high-velocity data ingestion, databases can temporarily reach up to 200% of their configured memory limit. This adaptive memory allocation strategy allows large amounts of data to be written to the database quickly without rejecting valid transactions.

Databases should return to their configured memory limits after data is removed according to the [eviction policy]({{<relref "/operate/rs/databases/memory-performance/eviction-policy/">}}) and [time-to-live (TTL)]({{<relref "/develop/use/keyspace#key-expiration">}}).

## Memory metrics

The Cluster Manager UI provides metrics that can help you evaluate your memory use.
Expand Down