Redis Enterprise allows the creation of Redis on Flash (RoF) databases that extend your caching DRAM capacity with Flash or SSD (Solid State Drives). Flash is a slower storage class than DRAM and persistent memory, enabling you to store significantly more data with fewer resources, reducing overall storage costs.
Redis on Flash is not designed to be used as an alternative mechanism for data persistence. The same Append Only File and snapshot data-persistence mechanisms, persisting data to disk, are used with Redis on Flash as with Redis Enterprise. RoF is based on the core Redis open source architecture with some primary enhancements:
This tiered storage architecture is shown here:
RoF is ideal for the following use cases:
RoF allows you to adjust your DRAM-to-Flash ratio without changing the memory quota (DRAM+Flash) of your database:
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-to-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.
The DRAM-to-Flash ratio adjustment is illustrated here:
RoF is built on a pluggable storage system architecture that supports the following storage engines by default:
Redis engineers have provided key fixes to these engines to make them compatible with Redis.
Redis on Flash is extremely fast; in well-optimized environments, RoF can run as fast as Redis on DRAM. In a recent benchmark performed over a single bare-metal Intel-based server equipped with Intel NVMe-based SSD cards, RoF achieved more than 3M ops/sec at sub-millisecond latency while transferring more than 1GB of data to and from the Flash memory:
Our engineers have conducted tests with the AWS’ I4i instances and with the RoF’s new Speedb data engine compared to AWS’ i3 instances. RoF is now even faster with the I4i instances, at 30% total cost of ownership of DRAM-based instances.
The graph below shows the scaling what AWS’ I4i on Speedb with different read:write ratios:
Watch our recent Tech Talk on 3 ways to cut IT costs with Redis Enterprise!
By continuing to use this site, you consent to our updated privacy agreement. You can change your cookie settings at any time but parts of our site will not function correctly without them.