Skip to content

Commit bf2f560

Browse files
committed
Fixed casing on the heading
1 parent 723eb90 commit bf2f560

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-cache-for-redis/cache-best-practices-server-load.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ High memory usage on the server makes it more likely that the system needs to pa
3535

3636
Redis server is a single-threaded system. Long running commands can cause latency or timeouts on the client side because the server can't respond to any other requests while it's busy working on a long running command. For more information, see [Troubleshoot Azure Cache for Redis server-side issues](cache-troubleshoot-server.md).
3737

38-
## Monitor server Load
38+
## Monitor Server Load
3939

4040
Add monitoring on server load to ensure you get notifications when high server load occurs. Monitoring can help you understand your application constraints. Then, you can work proactively to mitigate issues. We recommend trying to keep server load under 80% to avoid negative performance effects.
4141

0 commit comments

Comments
 (0)