Skip to content

Commit 818e9b0

Browse files
authored
heading capitalization
1 parent 8f1ee81 commit 818e9b0

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ ms.author: joncole
2020
# Best practices for Azure Cache for Redis
2121
By following these best practices, you can help maximize the performance and cost-effective use of your Azure Cache for Redis instance.
2222

23-
## Configuration and Concepts
23+
## Configuration and concepts
2424
* **Use Standard or Premium tier for production systems.** The Basic tier is a single node system with no data replication and no SLA. Also, use at least a C1 cache. C0 caches are meant for simple dev/test scenarios since they have a shared CPU core, little memory, and are prone to "noisy neighbor" issues.
2525

2626
* **Remember that Redis is an in-memory data store.** [This article](https://gist.github.com/JonCole/b6354d92a2d51c141490f10142884ea4#file-whathappenedtomydatainredis-md) outlines some scenarios where data loss can occur.
@@ -95,4 +95,4 @@ This will test GET requests using a 1k payload.
9595
9696
**To test throughput:**
9797
This uses Pipelined GET requests with 1k payload.
98-
> redis-benchmark.exe -h yourcache.redis.cache.windows.net -a yourAccesskey -t GET -n 1000000 -d 1024 -P 50 -c 50
98+
> redis-benchmark.exe -h yourcache.redis.cache.windows.net -a yourAccesskey -t GET -n 1000000 -d 1024 -P 50 -c 50

0 commit comments

Comments
 (0)