When to use RoF
RoF is ideal for the following use cases:
When your working set is significantly smaller than your dataset
When the average size of your keys is smaller than the average size of your values
When your database size (dataset + replication) is more than 100GB
When not to use RoF:
When the access to your dataset objects is completely random, i.e. your working set is the size of your dataset
When the average size of the keys in the dataset is about the same as that of the values
When the dataset size is small and has extremely high throughput requirements (>1M ops/sec)
Adjusting the DRAM-to-Flash ratio
RoF allows you to adjust your DRAM-to-Flash ratio without changing the memory quota (DRAM+Flash) of your database:
You can add more DRAM to your quota if more throughput is needed or latency must be reduced
You can add more Flash to your quota if you are satisfied with your performance but would like to use less cluster resources
Note 1: DRAM-to-Flash is automatically adjusted for you when using Redis Enterprise as a fully managed service in a virtual private cloud (VPC). For on-premises/self-managed deployments, adjusting your DRAM:Flash ratio is as easy as moving a slider.
Note 2: A scale-out process may be triggered when adding more DRAM to your memory quota, and a scale-in process may be triggered when adding more Flash to your memory quota. These processes will be completely automated when using Redis Enterprise as a fully managed service on your VPC, but require manual intervention when Redis Enterprise software is self-deployed.
