Skip to content

Commit 14b2152

Browse files
committed
touchup
1 parent 7af39b5 commit 14b2152

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/azure-cache-for-redis/cache-best-practices-memory-management.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ description: Learn how to manage your Azure Cache for Redis memory effectively.
66
ms.topic: conceptual
77
ms.custom:
88
- ignite-2024
9-
ms.date: 04/11/2025
9+
ms.date: 04/14/2025
1010
appliesto:
1111
- ✅ Azure Cache for Redis
1212

@@ -51,9 +51,9 @@ Consider how changing a `maxmemory-reserved` or `maxfragmentationmemory-reserved
5151
Eviction can increase server load and memory fragmentation. For more information on cache metrics such as `used_memory` and `used_memory_rss`, see [Create your own metrics](/azure/redis/monitor-cache#create-your-own-metrics).
5252

5353
> [!NOTE]
54-
> When you scale a cache up or down programmatically by using Azure PowerShell, Azure CLI, or REST API, any `maxmemory-reserved` and `maxfragmentationmemory-reserved` settings are ignored as part of the update request. Only your scaling change is honored. You can update the memory settings after the scaling operation completes.
54+
> When you scale a cache up or down programmatically by using Azure PowerShell, Azure CLI, or REST API, any included `maxmemory-reserved` or `maxfragmentationmemory-reserved` settings are ignored as part of the update request. Only your scaling change is honored. You can update the memory settings after the scaling operation completes.
5555
56-
## Next steps
56+
## Related content
5757

5858
- [Memory policies](cache-configure.md#memory-policies)
5959
- [Troubleshoot high memory usage](cache-troubleshoot-timeouts.md#high-memory-usage)

0 commit comments

Comments
 (0)