Documentation - Redise Pack

A guide to Redise Pack installation, operation and administration

open all | close all

Redise Flash Storage and Flash Memory Considerations

Unlike standard Redise Pack installations, implementing Redise Flash requires pre-planning around memory and sizing.  This page helps explain the recommendations and fundamentals that you need for a successful implementation of Redise Flash.

When implementing Redise Pack with Redise Flash, we strongly recommend that you configure Flash memory (SSDs) that is only for Redise Flash. Flash memory is used by Redise Pack to extend the database to be RAM + Flash Memory. It is strongly recommended that the flash memory be local to the server/instance, as well as dedicated to Redise Flash. This will help reduce latency and resource contention while providing the best performance for database operations.

For more information on Ephemeral and Persistent Storage in Redise Pack, please go here.


When running on a cloud environment, the flash memory for Redise Flash should be on the ephemeral SSDs of the cloud instance and persistent database storage should be network attached, e.g AWS EBS. For AWS, we specifically recommend “Storage Optimized I3 – High I/O Instances” because of the performance of NVMe for flash memory.

When running Redise Flash on-premise, it is best to use local internal flash memory in each server (preferably NVMe SSDs for their exceptional performance). The Redise Pack database persistent and ephemeral storage can be on different disks, either local or attached.

When you begin planning the deployment of Redise Flash in Production, we recommend working closely with the Redis Labs technical team for sizing and performance tuning.