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
Copy file name to clipboardExpand all lines: articles/redis/how-to-scale.md
+25-36Lines changed: 25 additions & 36 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,8 @@ Azure Managed Redis supports scaling in two dimensions:
29
29
30
30
-**Memory** Increasing memory increases the size of the Redis instance, allowing you to store more data. When reducing the memory, you need to ensure that your current memory usage is less than new memory size you want to use.
31
31
32
-
-**vCPUs** Azure Managed Redis offers three tiers (_Memory Optimized_, _Balanced_, and _Compute Optimized_) that have an increasing number of vCPUs for each level of memory. Scaling to a tier with more vCPUs increases the performance of your instance without requiring you to increase memory. Unlike the community edition of Redis, which can only utilize a single vCPU, Azure Managed Redis uses the Redis Enterprise stack, which is able to use multiple vCPUs. This means that the number of vCPUs used by your Redis instance directly correlates with throughput and latency performance.
32
+
-**vCPUs** Azure Managed Redis offers three tiers (_Memory Optimized_, _Balanced_, and _Compute Optimized_) that have an increasing number of vCPUs for each level of memory. Scaling to a tier with more vCPUs increases the performance of your instance without requiring you to increase memory. Unlike the community edition of Azure Cache for Redis, which can only utilize a single vCPU, Azure Managed Redis uses the Redis Enterprise stack, which is able to use multiple vCPUs. This means that the number of vCPUs used by your Redis instance directly correlates with throughput and latency performance.
33
+
<!-- Community edition means what here? Basic, Standard and Premium? -->
33
34
34
35
## Performance tiers
35
36
@@ -45,6 +46,8 @@ One tier stores data both in-memory and on-disk:
45
46
46
47
-_Flash Optimized_. Enables Redis clusters to automatically move less frequently accessed data from memory (RAM) to NVMe storage. This reduces performance, but allows for cost-effective scaling of caches with large datasets.
:::image type="content" source="media/how-to-scale/tier-diagram.png" alt-text="Table showing the different memory and vCPU configurations for each SKU and tier of Azure Managed Redis.":::
@@ -60,9 +63,9 @@ You can use the [monitoring](monitor-cache.md) features of Azure Managed Redis t
60
63
You can monitor the following metrics to determine if you need to scale.
61
64
62
65
-**CPU**
63
-
- High CPU usage means that the Redis server is unable to keep pace with requests from all the clients. Scaling up to more vCPUs helps distribute requests across multiple Redis processes. Scaling also helps distribute TLS encryption/decryption and connection/disconnection, speeding up cache instances using TLS.
66
+
- High CPU usage means that the Redis server is unable to keep pace with requests from all the clients. Scaling to more vCPUs helps distribute requests across multiple Redis processes. Scaling also helps distribute TLS encryption/decryption and connection/disconnection, speeding up cache instances using TLS.
64
67
-**Memory Usage**
65
-
- High memory usage indicates that your data size is too large for the current cache size. Consider scaling to a cache size with larger memory. When reducing the memory, you need to ensure that your current memory usage is less than new memory size you want to use.
68
+
- High memory usage indicates that your data size is too large for the current cache size. Consider scaling to a cache size with larger memory. When reducing the memory, you need to ensure that your memory usage or your current cache is lower than new memory size you want to use. You cannot put a large data set into a smaller cache size.
66
69
-**Client connections**
67
70
- Each cache size has a limit to the number of client connections it can support. If your client connections are close to the limit for the cache size, consider scaling to a larger memory size or a higher performance tier.
68
71
- For more information on connection limits by cache size, see [Performance testing with Azure Managed Redis](best-practices-performance.md).
@@ -73,19 +76,18 @@ You can monitor the following metrics to determine if you need to scale.
73
76
74
77
For more information on determining the cache pricing tier to use, see [Choosing the right tier](overview.md#choosing-the-right-tier).
75
78
76
-
> [!NOTE]
77
-
> For more information on how to optimize the scaling process, see the [best practices for scaling guide](best-practices-scale.md)
78
-
>
79
+
For more information on how to optimize the scaling process, see the [best practices for scaling guide](best-practices-scale.md)
79
80
80
81
## Limitations of scaling Azure Managed Redis
81
82
82
83
- You can't scale from the **Memory Optimized**, **Balanced**, or **Compute Optimized** tiers to the **Flash Optimized** tier, or vice-versa.
83
-
- When reducing the memory for your Redis instance, the current memory usage of your Redis instance should be less than the intended new memory size. See [this](#what-will-happen-to-my-data-if-i-scale-to-smaller-memory-size) for more details.
84
-
- When reducing the memory or vCPU for your Redis instance, you can only scale to SKUs which have a vCPU and shard configuration that is compatible with the configuration on your current instance. See this [table](add link) for a guideline on which SKUs can you scale down your Redis instance to.
84
+
- When reducing the memory for your Redis instance, the current memory usage of your Redis instance should be less than the intended new memory size. For more details, see [What will happen to my data if I scale to smaller memory size?](#what-will-happen-to-my-data-if-i-scale-to-smaller-memory-size).
85
+
- When reducing the memory or vCPU for your Redis instance, you can only scale to SKUs which have a vCPU and shard configuration that is compatible with the configuration on your current instance.
86
+
<!-- We removed the table so we need to find a way convey this information -->
85
87
- In some cases when scaling, the underlying IP address of the Redis instance can change. The DNS record for the instance changes and is transparent to most applications. However, if you use an IP address to configure the connection to your Redis instance, or to configure NSGs, or firewalls allowing traffic to the Redis instance, your application might have trouble connecting sometime after the DNS record updates.
86
88
- Scaling an instance in a geo-replication group has some more limitations. See [Are there scaling limitations with geo-replication?](#are-there-scaling-limitations-with-geo-replication) for more information.
87
89
88
-
## How to scale
90
+
## How to scale (preview)
89
91
90
92
### Scale using the Azure portal
91
93
@@ -94,16 +96,17 @@ For more information on determining the cache pricing tier to use, see [Choosing
94
96
:::image type="content" source="media/how-to-scale/managed-redis-enterprise-scale.png" alt-text="Screenshot showing Scale selected in the Resource menu for an Enterprise cache.":::
95
97
96
98
1. To scale your vCPUs, choose a different **Cache type** and then choose **Save**.
99
+
97
100
> [!IMPORTANT]
98
-
> If you select a SKU that cannot be scaled to, the **Save** option is disabled. Review the [Limitations of scaling Azure Managed Redis](#prerequisiteslimitations-of-scaling-azure-managed-redis) section for details on which scaling options are allowed.
101
+
> If you select a SKU that cannot be scaled to, the **Save** option is disabled. Review the [Limitations of scaling Azure Managed Redis](#limitations-of-scaling-azure-managed-redis) section for details on which scaling options are allowed.
99
102
100
103
:::image type="content" source="media/how-to-scale/managed-redis-enterprise-scale-up.png" alt-text="Screenshot showing the Enterprise tiers in the working pane.":::
101
104
102
105
1. While the cache is scaling to the new tier, a **Scaling Redis Cache** notification is displayed.
103
106
104
107
:::image type="content" source="media/how-to-scale/managed-redis-enterprise-notifications.png" alt-text="Screenshot showing notification of scaling an Enterprise cache.":::
105
108
106
-
1. When scaling is complete, the status on the Overview blade changes from **Scaling** to **Running**.
109
+
1. When scaling is complete, the status changes from **Scaling** to **Running** when viewing the **Overview** section of the Resource menu.
107
110
108
111
### Scale using PowerShell
109
112
@@ -142,45 +145,31 @@ The following list contains answers to commonly asked questions about Azure Mana
142
145
143
146
### Can I scale within or across tiers?
144
147
145
-
You can always scale to a higher performance tier at the same memory size or a larger memory size within the same performance tier. For scaling to a lower performance tier or smaller memory size, see the table below for SKUs that your cluster can scale to. Please note that this table is just a guidance and we recommend you run the "listskusforscaling" REST API to get the list of SKUs that you can scale to.
You can always scale to a higher performance tier at the same memory size or a larger memory size within the same performance tier. For scaling to a lower performance tier or smaller memory size, we recommend you run the "listskusforscaling" REST API to get the list of SKUs that you can scale to.
149
+
<!-- Perhaps we can add some code or cli commands to show this. -->
164
150
165
151
### What will happen to my data if I scale to smaller memory size?
166
152
167
-
You can scale to a smaller memory size only if the current memory usage is less than the intended smaller memory size. If the current memory usage is higher than the intended smaller size, your scaling request will fail. You can reduce the current memory usage by deleted unwanted key value pairs or by running the flush operation. (Add link)
153
+
You can scale to a smaller memory size only if the current memory usage is less than the intended smaller memory size. If the current memory usage is higher than the intended smaller size, your scaling request will fail. You can reduce the current memory usage by deleted unwanted key value pairs or by running the flush operation.
154
+
155
+
<!-- (Add link) -->
168
156
169
157
### After scaling, do I have to change my cache name or access keys?
170
158
171
-
No, your cache name and keys are unchanged during a scaling operation.
159
+
No, your cache name and access keys are not changed during a scaling operation.
172
160
173
161
### How does scaling work?
174
162
175
-
- When you scale a Redis instance, one of the nodes in the Redis cluster is shut down and reprovisioned to the new size. Then data transferred over, and then the other node does a similar failover before it's reprovisioned. This is similar to the process that occurs during patching or a failure of one of the cache nodes.
163
+
- When you scale a Redis instance, one of the nodes in the Redis cluster is shut down and reprovisioned to the new size. Then data transfers over, and the other node does a similar failover subsequently before it's reprovisioned. This is similar to the process that occurs during patching or a failure of one of the cache nodes.
176
164
- When scaling to an instance with more vCPUs, new shards are provisioned and added to the Redis server cluster. Data is then resharded across all shards.
177
165
178
166
For more information on how Azure Managed Redis handles sharding, see [Sharding configuration](architecture.md#sharding-configuration).
179
167
180
168
### Do I lose data from my cache during scaling?
181
169
182
170
- If high availability mode is enabled, all data should be preserved during scaling operations.
183
-
- If you're scaling to a smaller memory level, you need to ensure that the current memory usage is lower than the intended new memory size. If the current memory usage is more than the intended SKU memory size, you can flush your data using Flush operation (add link) or choose key values to delete manually.
171
+
- If you're scaling to a smaller memory level, you need to ensure that the current memory usage is smaller than the intended new memory size. If the current memory usage is more than the intended SKU memory size, you can flush your data using Flush operation or manually choose key values to delete.
172
+
<!-- - add link -->
184
173
- If high availability mode is disabled, all data is lost and the cache is unavailable during the scaling operation.
185
174
186
175
### Will my cache be available during scaling?
@@ -204,7 +193,7 @@ Generally, when you scale an instance with no data, it takes approximately 10 mi
204
193
205
194
### How can I tell when scaling is complete?
206
195
207
-
In the Azure portal, you can see the scaling operation in progress. When scaling is complete, the status of the cache changes to **Running**.
196
+
In the Azure portal, you can see the scaling operation in progress. When scaling is complete, the status of the cache changes to **Running** when viewing **Overview** on the Resource menu.
208
197
209
198
### Does Azure Managed Redis use clustering?
210
199
@@ -229,6 +218,6 @@ For more information, see [Keys distribution model](https://redis.io/topics/clus
229
218
230
219
The largest cache size you can have is 4.5 TB, called Flash Optimized A4500 instance. [Azure Cache for Redis Pricing](https://azure.microsoft.com/pricing/details/cache/).
231
220
232
-
## Next steps
221
+
## Related content
233
222
234
223
-[Best practices for scaling](best-practices-scale.md)
0 commit comments