Skip to content

Commit 2cad073

Browse files
Merge pull request #287906 from flang-msft/fxl---improve-time-to-scale-language--WI-28872436
fxl---updated scale time language
2 parents 294e43c + 7d3fd28 commit 2cad073

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/azure-cache-for-redis/cache-how-to-scale.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -369,7 +369,9 @@ Scaling time depends on a few factors. Here are some factors that can affect how
369369
- High write requests: Higher number of writes mean more data replicates across nodes or shards
370370
- High server load: Higher server load means the Redis server is busy and limited CPU cycles are available to complete data redistribution
371371

372-
Generally, when you scale a cache with no data, it takes approximately 20 minutes. For clustered caches, scaling takes approximately 20 minutes per shard with minimal data.
372+
Scaling a cache is non-trivial action and can take a long time.
373+
374+
Based on real world examples, the time to scale cache with one to two shards can be 1 to 2 hours when the cache is not under heavy loads.If you have more shards, the time to scale doesn't increase in a linear way.
373375

374376
### How can I tell when scaling is complete?
375377

0 commit comments

Comments
 (0)