Conversation
🛡️ Jit Security Scan Results
✅ No security findings were detected in this PR
Security scan by Jit
|
|
@rrelledge the screenshot for the "create a database" step is really large. You could scale it down to half that size I think |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 3 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
| - Reduce infrastructure costs by combining high-speed RAM with cost-efficient flash storage | ||
|
|
||
| {{<note>}} | ||
| Flex does not replace long-term data persistence. For workloads that require durability and recovery across restarts or failures, use Redis persistence features like [AOF (Append-Only File)]({{< relref "/operate/oss_and_stack/management/persistence#append-only-file" >}}), [RDB snapshots]({{< relref "/operate/oss_and_stack/management/persistence#snapshotting" >}}), or both. For more information, see [Database persistence]({{< relref "/operate/rs/databases/configure/database-persistence" >}}). |
There was a problem hiding this comment.
I suggest adding a dedicated "What Flex isn't" section with the wording similar to the doc: https://docs.google.com/document/d/1PuFejCooJpy_gs0MoM5Pf9MLS46x6gcNUmzYfPjIHik/edit?disco=AAABz_t08H0&tab=t.0
|
|
||
| ### Differences between Flex and Auto Tiering | ||
|
|
||
| - Key and value offloading |
There was a problem hiding this comment.
Add a short explanation on why it matters:
"frees RAM for hot data, higher RAM hit‑rate, bigger datasets per node”
| --- | ||
|
|
||
| Flex extends your database capacity by combining RAM and flash (SSD) storage. This tiered architecture keeps frequently accessed (hot) data in RAM for sub-millisecond latency while storing less active (warm) data on flash to reduce costs and increase capacity. | ||
|
|
There was a problem hiding this comment.
"Flex frees RAM for hot data, higher RAM hit‑rate, bigger datasets per node”
3 participants
Still a work in progress
Note
Low Risk
Docs-only additions with no product code changes; main risk is incorrect guidance or broken cross-links/anchors.
Overview
Adds a new
operate/rs/flexdocumentation section introducing Flex databases (tiered RAM+flash/SSD) for Redis Software.Includes new pages covering how Flex works and how it differs from Auto Tiering, plus practical guidance for planning (version/hardware/sizing/limitations), getting started (install, prepare flash, create/connect to a Flex DB), and scaling strategies (capacity/throughput/infrastructure).
Written by Cursor Bugbot for commit 0a9fc1e. This will update automatically on new commits. Configure here.