Skip to content

Commit bcc398d

Browse files
shpathak-msftshpathak-msft
committed
add table
1 parent d14d4ff commit bcc398d

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

‎articles/redis/how-to-scale.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -141,6 +141,24 @@ The following list contains answers to commonly asked questions about Azure Mana
141141

142142
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.
143143

144+
| **Size (GB)** | **Memory Optimized** | **Balanced** | **Compute Optimized** |
145+
|---------------|----------------------------------------------------------------------------------|--------------------------------------------------------------------------|-----------------------------------------------------------------------------------|
146+
| **0.5** | - | - | - |
147+
| **1** | - | B0 | - |
148+
| **3** | | B1, B0 | B3, B1, B0 |
149+
| **6** | B5, B3, B1, B0<br>X5, X3 | M10<br>B5, B3, B1, B0<br>X5, X3 | M10<br>B10, B5, B3, B1, B0<br>X5, X3 |
150+
| **12** | M10<br>B10, B5, B3, B1, B0<br>X10, X5, X3 | M20, M10<br>B10, B5, B3, B1, B0<br>X10, X5, X3 | M20, M10<br>B20, B10, B5, B3, B1, B0<br>X10, X5, X3 |
151+
| **24** | M20, M10<br>B20, B10, B5, B3, B1, B0<br>X20, X10, X5, X3 | M50, M20, M10<br>B20, B10, B5, B3<br>X20, X10, X5, X3 | M50<br>B50, B20<br>X20, X10 |
152+
| **60** | M50, M20, M10<br>B50, B20, B10, B5, B3<br>X50, X20, X10, X5, X3 | M100, M50<br>B50, B20<br>X20, X10 | M100<br>B100, B50<br>X50, X20 |
153+
| **120** | M100, M50<br>B100, B50, B20<br>X100, X50, X20, X10 | M150, M100<br>B100, B50<br>X100, X50, X20 | M150<br>B150, B100<br>X100, X50 |
154+
| **180** | M150, M100, M50<br>B150, B100, B50, B20<br>X150, X100, X50, X20, X10 | M200, M150, M100<br>B150, B100, B50<br>X150, X100, X50, X20 | M200, M150<br>B200, B150, B100<br>X150, X100, X50 |
155+
| **240** | M200, M150, M100<br>B200, B150, B100, B50<br>X200, X150, X100, X50, X20 | M350, M200, M150, M100<br>B200, B150, B100<br>X200, X150, X100, X50 | M350<br>B350, B200, B150<br>X200, X150, X100 |
156+
| **360** | M350, M200, M150, M100<br>B350, B200, B150, B100, B50<br>X350, X200, X150, X100 | M500, M350, M200, M150<br>B350, B200, B150, B100<br>X350, X200, X150, X100, X50 | M500, M350<br>B350, B200, B150<br>X350, X200, X150, X100 |
157+
| **480** | M500, M350, M200, M150<br>B500, B350, B200, B150, B100<br>X500, X350, X200, X150, X100, X50 | M700, M500, M350<br>B500, B350, B200, B150<br>X350, X200, X150, X100 | M700, M500, M350<br>B350, B200, B150<br>X500, X350, X200, X150, X100 |
158+
| **720** | M700, M500, M350, M200, M150<br>B700, B500, B350, B200, B150, B100<br>X700, X500, X350, X200, X150, X100, X50 | M1000, M700, M500, M350<br>B1000, B700, B500, B350, B200, B150<br>X700, X500, X350, X200, X150, X100 | |
159+
| **960** | M1000, M700, M500, M350<br>B1000, B700, B500, B350, B200, B150<br>X700, X500, X350, X200, X150, X100 | - | |-
160+
| **1440** | M1000, M700, M500, M350<br>B1000, B700, B500, B350, B200, B150<br>X700, X500, X350, X200, X150, X100 | - | - |
161+
144162
### What will happen to my data if I scale to smaller memory size?
145163

146164
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)

0 commit comments

Comments
 (0)