You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-cache-for-redis/cache-best-practices-performance.md
+19-1Lines changed: 19 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,6 +71,19 @@ Pipelined GET requests with 1k payload:
71
71
```dos
72
72
redis-benchmark -h yourcache.redis.cache.windows.net -a yourAccesskey -t GET -n 1000000 -d 1024 -P 50 -c 50
73
73
```
74
+
75
+
**To test throughput of a Basic, Standard, or Premium tier cache using TLS:**
76
+
Pipelined GET requests with 1k payload:
77
+
```dos
78
+
redis-benchmark -h yourcache.redis.cache.windows.net -p 6380 -a yourAccesskey -t GET -n 1000000 -d 1024 -P 50 -c 50 --tls
79
+
```
80
+
81
+
**To test throughput of an Enterprise or Enterprise Flash cache without TLS using OSS Cluster Mode:**
82
+
Pipelined GET requests with 1k payload:
83
+
```dos
84
+
redis-benchmark -h yourcache.region.redisenterprise.cache.azure.net -p 10000 -a yourAccesskey -t GET -n 1000000 -d 1024 -P 50 -c 50 --cluster
85
+
```
86
+
74
87
## Example performance benchmark data
75
88
76
89
The following tables show the maximum throughput values that were observed while testing various sizes of Standard, Premium, Enterprise, and Enterprise Flash caches. We used `redis-benchmark` from an IaaS Azure VM against the Azure Cache for Redis endpoint. The throughput numbers are only for GET commands. Typically, SET commands have a lower throughput. These numbers are optimized for throughput. Real-world throughput under acceptable latency conditions may be lower.
@@ -110,7 +123,11 @@ redis-benchmark -h yourcache.redis.cache.windows.net -a yourAccesskey -t GET -n
110
123
> [!Important]
111
124
> P5 instances in the China East and China North regions use 20 cores, not 32 cores.
112
125
113
-
### Enterprise tier
126
+
### Enterprise tier - Enterprise Cluster Policy
127
+
128
+
> [!IMPORTANT]
129
+
> The Enterprise and Enterprise Flash tiers offer a choice of cluster policy: _Enterprise_ and _OSS_.
130
+
114
131
| Instance | Size | vCPUs | Network bandwidth (Mbps)| GET requests per second without SSL (1 kB value size) | GET requests per second with SSL (1 kB value size) |
115
132
| --- | --- | --- | --- | --- | --- |
116
133
| P1 | 6 GB | 2 | 1,500 | 180,000 | 172,000 |
@@ -119,6 +136,7 @@ redis-benchmark -h yourcache.redis.cache.windows.net -a yourAccesskey -t GET -n
0 commit comments