Conversation
…and Flex databases
🛡️ Jit Security Scan Results
✅ No security findings were detected in this PR
Security scan by Jit
|
![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 using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 9850baf. Configure here.
| - For the best performance, the SSDs should be NVMe based. NVMe Gen 5 or Gen 4 is recommended. Gen 3 is also supported, but not recommended for best performance. | ||
|
|
||
| - Flash storage must be greater than the total provisioned database size to account for write buffers, space amplification, and more. | ||
| - Flash storage must be greater than the total provisioned database size to account for write buffers, space amplification, and more. Flash space should be approximately three times the total memory limit of all Flex databases on the node. Because you can increase a database's memory limit after creation, size flash storage for the expected peak memory limit. |
There was a problem hiding this comment.
Conflicting Flex flash sizing rules
High Severity
The updated hardware requirements bullet still requires Flex flash to be greater than a single database’s provisioned size, while the same change set defines the minimum as three times the total memory limit of all Flex databases on the node. On nodes with multiple Flex databases, the weaker rule can be read as sufficient and lead to severe under-provisioning.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 9850baf. Configure here.
2 participants
Note
Low Risk
Documentation-only changes to sizing guidance; no code or runtime behavior.
Overview
Documentation now treats local SSD sizing differently for Auto Tiering versus Flex, instead of a single combined “Redis Flex and Auto Tiering” row.
The production hardware table adds a dedicated Flex local-disk row (3× the total memory limit of all Flex databases on the node, min and recommended) and keeps Auto Tiering on (RAM+Flash) × 1.6 / 2.5, with a new footnote to size Flex disk for expected peak memory limits after increases.
The same split appears in flash/memory-limit guidance (section retitled to flash-enabled databases) and Flex plan hardware bullets, each clarifying Auto Tiering’s RAM+Flash floor vs Flex’s node-level 3× memory-limit rule.
Reviewed by Cursor Bugbot for commit 9850baf. Bugbot is set up for automated code reviews on this repo. Configure here.