Test Data of Proxy Cluster DCS Redis 3.0 Instances
Test Environment
Test Command
./redis-benchmark -h {IP} -p {Port} -a {password} -n {nreqs} -r {randomkeys} -c {connection} -d {datasize} -t {command} Reference values: -c {connect_number}: 1000; -n {nreqs}: 10,000,000; -r {randomkeys}: 1,000,000; -d {datasize}: 32
Test Result
| Redis Cache Size | CPU Type | Concurrent Connections | QPS | 99.99th-Percentile Latency (ms) | First 100th-Percentile Latency (ms) | Last 100th-Percentile Latency (ms) |
|---|---|---|---|---|---|---|
| 64 GB | x86 | 1000 | 534,960.92 | 24 | 34 | 209 |
| 10,000 | 511,362.67 | 108 | 171 | 315 |
| Redis Cache Size | CPU Type | Concurrent Connections | QPS | 99.99th-Percentile Latency (ms) | First 100th-Percentile Latency (ms) | Last 100th-Percentile Latency (ms) |
|---|---|---|---|---|---|---|
| 64 GB | x86 | 1000 | 584,669.15 | 23 | 31 | 82 |
| 10,000 | 533,178.04 | 144 | 184 | 370 |
DCS for Redis 3.0 does not support the Arm CPU architecture, so only x86-based instance test results are provided.
Last Article: Test Data of Master/Standby DCS Redis 3.0 Instances
Next Article: Test Data of Master/Standby DCS Redis 4.0 or 5.0 Instances
Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.