Document Flex best practices and limitations - #3920
Merged
Merged
Conversation
Add key/value size guidance and the 4 GB Flash storage limit (larger values fall back to RAM-only with a log warning), plus clarify that the Essentials RAM percentage is fixed at 10% versus Pro's configurable 10-50% range. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
Contributor
🧠 Redis MemoryFound 7 related items from repository history (2 new this commit):
Memory updated at 7b5b43f |
Contributor
andy-stark-redis
approved these changes
Sep 4, 2026
andy-stark-redis
left a comment
andy-stark-redis
left a comment
Contributor
There was a problem hiding this comment.
Minor suggestion but basically LGTM.
…ase.md Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
EliShteinman
added a commit
to EliShteinman/docs
that referenced
this pull request
Sep 5, 2026
Documents the Flex RAM percentage per plan and the object size guidance, including the 4 GB ceiling above which keys stay in RAM and log a warning. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WycKvjyQaCQQBwVEkvSAKT
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Add key/value size guidance and the 4 GB Flash storage limit (larger values fall back to RAM-only with a log warning), plus clarify that the Essentials RAM percentage is fixed at 10% versus Pro's configurable 10-50% range.
Note
Low Risk
Documentation-only change with no runtime, API, or configuration behavior changes.
Overview
Adds a Best practices and limitations section to the Redis Cloud Flex database creation guide, before the existing create steps.
It documents RAM percentage rules: Essentials Flex is fixed at 10% (not configurable), while Pro allows 10–50% at creation, with a link to support guidance on choosing a ratio.
It adds key and value size guidance: prefer small objects (avoid >10 KB) because tiering moves whole values between RAM and Flash; Flash cannot hold keys/values over 4 GB (those stay RAM-only and log a
key too big for disk driverwarning), including an example log line.Reviewed by Cursor Bugbot for commit 7b5b43f. Bugbot is set up for automated code reviews on this repo. Configure here.