When designing for production, there are key performance topics that you should read up on.
In Redis Enterprise Software (RS), the location of master and slave shards on the cluster nodes can impact the database and node performance. Master shards and their corresponding slave shards are always placed on separate nodes for data resiliency. The shard placement policy helps to maintain optimal performance and resiliency. In addition to the shard placement policy, considerations that determine shard placement are: Separation of master and slave shards Available persistence and Redis on Flash (RoF) storage Rack awareness Memory available to host the database when fully populated The shard placement policies are:
In extreme write scenarios, when AOF is enabled, the AOF rewrite process may require considerably more disk space for database persistence. To estimate the required persistent disk space in such cases, use the formula described below. The required persistent disk space for AOF rewrite purposes in extreme write scenarios, assuming identical shard sizes: X (1 + 3Y +Y²) where: X = each shard size Y = number of shards Following are examples of database configurations and the persistence disk space they would require in this scenario:
Redis Enterprise Software (RS) employs various algorithms to optimize performance. As part of this process, RS examines usage characteristics and load and adjusts its run-time configuration accordingly. Depending on your specific usage characteristics and load, it might take RS some time to adjust itself to optimal performance. To ensure optimal performance, you must run your workload several times and for a long duration until performance stabilizes. In addition, RS can be optimized for two different environments: