You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Auto Tiering enables your data to span both RAM and dedicated flash memory.
9
+
description: Redis Flex enables your data to span both RAM and dedicated flash memory.
10
10
hideListLinks: true
11
-
linktitle: Auto Tiering
11
+
linktitle: Redis Flex
12
12
weight: 50
13
+
aliases: /operate/rs/databases/auto-tiering/
13
14
---
14
-
Redis Enterprise's auto tiering offers users the unique ability to use solid state drives (SSDs) to extend databases beyond DRAM capacity.
15
+
Redis Flex (previously known as auto tiering) offers users the unique ability to use solid state drives (SSDs) to extend databases beyond DRAM capacity.
15
16
Developers can build applications that require large datasets using the same Redis API.
16
17
Using SSDs can significantly reduce the infrastructure costs compared to only DRAM deployments.
17
18
18
19
Frequently used data, called hot data, belongs in the fastest memory level to deliver a real-time user experience.
19
20
Data that is accessed less frequently, called warm data, can be kept in a slightly slower memory tier.
20
-
Redis Enterprise’s Auto tiering maintains hot data in DRAM, keeps warm data in SSDs, and transfers data between tiers automatically.
21
+
Redis Flex maintains hot data in DRAM, keeps warm data in SSDs, and transfers data between tiers automatically.
21
22
22
-
Redis Enterprise’s auto tiering is based on a high-performance storage engine (Speedb) that manages the complexity of using SSDs and DRAM as the total available memory for databases in a Redis Enterprise cluster. This implementation offers a performance boost of up to 10k operations per second per core of the database, doubling the performance of Redis on Flash.
23
+
Redis Flex is based on a high-performance storage engine (Speedb) that manages the complexity of using SSDs and DRAM as the total available memory for databases in a Redis Enterprise cluster. This implementation offers a performance boost of up to 10k operations per second per core of the database, doubling the performance of Redis on Flash.
23
24
24
-
Just like all-RAM databases, databases with Auto Tiering enabled are compatible with existing Redis applications.
25
+
Just like all-RAM databases, Redis Flex databases are compatible with existing Redis applications.
25
26
26
-
Auto Tiering is also supported on [Redis Cloud]({{< relref "/operate/rc/" >}}) and [Redis Enterprise Software for Kubernetes]({{< relref "/operate/rs/" >}}).
27
+
Redis Flex is also supported on [Redis Cloud]({{< relref "/operate/rc/" >}}) and [Redis Enterprise Software for Kubernetes]({{< relref "/operate/rs/" >}}).
27
28
28
29
## Use cases
29
30
30
-
The benefits associated with Auto Tiering are dependent on the use case.
31
+
The benefits associated with Redis Flex are dependent on the use case.
31
32
32
-
Auto Tiering is ideal when your:
33
+
Redis Flex is ideal when your:
33
34
34
35
- working set is significantly smaller than your dataset (high RAM hit rate)
35
36
- average key size is smaller than average value size (all key names are stored in RAM)
36
37
- most recent data is the most frequently used (high RAM hit rate)
37
38
38
-
Auto Tiering is not recommended for:
39
+
Redis Flex is not recommended for:
39
40
40
41
- Long key names (all key names are stored in RAM)
41
42
- Broad access patterns (any value could be pulled into RAM)
42
43
- Large working sets (working set is stored in RAM)
43
44
- Frequently moved data (moving to and from RAM too often can impact performance)
44
45
45
-
Auto Tiering is not intended to be used for persistent storage. Redis Enterprise Software database persistent and ephemeral storage should be on different disks, either local or attached.
46
+
Redis Flex is not intended to be used for persistent storage. Redis Enterprise Software database persistent and ephemeral storage should be on different disks, either local or attached.
46
47
47
48
## Where is my data?
48
49
49
-
When using Auto Tiering, RAM storage holds:
50
+
When using Redis Flex, RAM storage holds:
50
51
- All keys (names)
51
52
- Key indexes
52
53
- Dictionaries
@@ -56,7 +57,7 @@ All data is accessed through RAM. If a value in flash memory is accessed, it bec
56
57
57
58
Inactive or infrequently accessed data is referred to as "warm data" and stored in flash memory. When more space is needed in RAM, warm data is moved from RAM to flash storage.
58
59
59
-
{{<note>}} When using Auto Tiering with RediSearch, it’s important to note that RediSearch indexes are also stored in RAM.{{</note>}}
60
+
{{<note>}} When using Redis Flex with RediSearch, it’s important to note that RediSearch indexes are also stored in RAM.{{</note>}}
60
61
61
62
## RAM to Flash ratio
62
63
@@ -67,19 +68,19 @@ The RAM limit cannot be smaller than 10% of the total memory. We recommend you k
67
68
68
69
## Flash memory
69
70
70
-
Implementing Auto Tiering requires pre planning around memory and sizing. Considerations and requirements for Auto Tiering include:
71
+
Implementing Redis Flex requires pre planning around memory and sizing. Considerations and requirements for Redis Flex include:
71
72
72
73
- Flash memory must be locally attached. Using network-attached storage (NAS), storage area networks (SAN), or solutions such as AWS Elastic Block Storage (EBS) is not supported.
73
-
- Flash memory must be dedicated to Auto Tiering and not shared with other parts of the database, such as durability, binaries, or persistence.
74
+
- Flash memory must be dedicated to Redis Flex and not shared with other parts of the database, such as durability, binaries, or persistence.
74
75
- For the best performance, the SSDs should be NVMe based, but SATA can also be used.
75
76
- The available flash space must be greater than or equal to the total database size (RAM+Flash). The extra space accounts for write buffers and [write amplification](https://en.wikipedia.org/wiki/Write_amplification).
76
77
77
78
{{<note>}} The Redis Enterprise Software database persistent and ephemeral storage should be on different disks, either local or attached. {{</note>}}
78
79
79
-
Once these requirements are met, you can create and manage both databases with Auto Tiering enabled and
80
+
After these requirements are met, you can create and manage both Redis Flex databases and
80
81
all-RAM databases in the same cluster.
81
82
82
-
When you begin planning the deployment of an Auto Tiering enabled database in production,
83
+
When you begin planning the deployment of a Redis Flex database in production,
83
84
we recommend working closely with the Redis technical team for sizing and performance tuning.
84
85
85
86
### Cloud environments
@@ -94,7 +95,7 @@ We specifically recommend "[Storage Optimized I4i - High I/O Instances](https://
94
95
95
96
### On-premises environments
96
97
97
-
When you begin planning the deployment of Auto Tiering in production, we recommend working closely with the Redis technical team for sizing and performance tuning.
98
+
When you begin planning the deployment of Redis Flex in production, we recommend working closely with the Redis technical team for sizing and performance tuning.
98
99
99
100
On-premises environments support more deployment options than other environments such as:
100
101
@@ -105,13 +106,13 @@ On-premises environments support more deployment options than other environments
105
106
-[Probabilistic data structures]({{< relref "/operate/oss_and_stack/stack-with-enterprise/bloom" >}})
106
107
107
108
108
-
{{<note>}} Enabling Auto Tiering for [Active-Active distributed databases]({{<relref "/operate/rs/databases/active-active">}}) requires validating and getting the Redis technical team's approval first . {{</note>}}
109
+
{{<note>}} Enabling Redis Flex for [Active-Active distributed databases]({{<relref "/operate/rs/databases/active-active">}}) requires validating and getting the Redis technical team's approval first . {{</note>}}
109
110
110
-
{{<warning>}} Auto Tiering is not supported running on network attached storage (NAS), storage area network (SAN), or with local HDD drives. {{</warning>}}
111
+
{{<warning>}} Redis Flex is not supported running on network attached storage (NAS), storage area network (SAN), or with local HDD drives. {{</warning>}}
111
112
112
113
## Size limits for keys and values
113
114
114
-
Auto Tiering databases cannot store keys or values larger than 4GB in flash storage.
115
+
Redis Flex databases cannot store keys or values larger than 4GB in flash storage.
115
116
116
117
Keys or values larger than 4GB will be stored in RAM only, and warnings will appear in the Redis logs similar to:
117
118
@@ -121,8 +122,8 @@ Keys or values larger than 4GB will be stored in RAM only, and warnings will app
This page guides you through a quick setup of [Auto Tiering]({{< relref "/operate/rs/databases/auto-tiering/" >}}) with a single node for testing and demo purposes.
14
+
This page guides you through a quick setup of [Redis Flex]({{< relref "/operate/rs/databases/flash" >}}) with a single node for testing and demo purposes.
14
15
15
16
For production environments, you can find more detailed installation instructions in the [install and setup]({{< relref "/operate/rs/installing-upgrading" >}}) section.
16
17
17
-
The steps to set up a Redis Enterprise Software cluster using Auto Tiering
18
+
The steps to set up a Redis Enterprise Software cluster using Redis Flex
18
19
with a single node are:
19
20
20
21
1. Install Redis Enterprise Software or run it in a Docker
21
22
container.
22
-
1. Set up a Redis Enterprise Software cluster with Auto Tiering.
23
-
1. Create a new database with Auto Tiering enabled.
23
+
1. Set up a Redis Enterprise Software cluster with Redis Flex.
24
+
1. Create a new database with Redis Flex enabled.
24
25
1. Connect to your new database.
25
26
26
27
## Install Redis Enterprise Software
@@ -70,7 +71,7 @@ To verify the disk configuration, run:
70
71
sudo lsblk
71
72
```
72
73
73
-
## Set up a cluster and enable Auto Tiering
74
+
## Set up a cluster and enable Redis Flex
74
75
75
76
1. Direct your browser to `https://localhost:8443` on the host machine to
76
77
see the Redis Enterprise Software Cluster Manager UI.
@@ -111,12 +112,12 @@ On the **Databases** screen:
111
112
112
113
1. Select **Create**.
113
114
114
-
You now have a database with Auto Tiering enabled!
115
+
You now have a database with Redis Flex enabled!
115
116
116
117
## Connect to your database
117
118
118
119
After you create the database, you can connect to it and store data. See [Test client connection]({{<relref "/operate/rs/databases/connect/test-client-connectivity">}}) for connection options and examples.
119
120
120
121
## Next steps
121
122
122
-
To see the true performance and scale of Auto Tiering, you must tune your I/O path and set the flash path to the mounted path of SSD or NVMe flash memory as that is what it is designed to run on. For more information, see [Auto Tiering]({{< relref "/operate/rs/databases/auto-tiering/">}}).
123
+
To see the true performance and scale of Redis Flex, you must tune your I/O path and set the flash path to the mounted path of SSD or NVMe flash memory as that is what it is designed to run on. For more information, see [Redis Flex]({{< relref "/operate/rs/databases/redis-flex/">}}).
0 commit comments