Test Data of Master/Standby DCS Redis 3.0 Instances

Redis instance specifications
Redis 3.0 | 8 GB | master/standby

Redis 3.0 | 32 GB | master/standby
ECS flavors
General computing-enhanced | c6.xlarge.2 | 4 vCPUs | 8 GB

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

**Table 1** Test result of running the SET command
Redis Cache Size	CPU Type	Concurrent Connections	QPS	99.99^th-Percentile Latency (ms)	First 100^th-Percentile Latency (ms)	Last 100^th-Percentile Latency (ms)
8 GB	x86	1000	107,657.69	20	23	27
8 GB	x86	10,000	72,750.55	362	366	371
32 GB	x86	1000	121,088.83	9	12	12
32 GB	x86	10,000	79,235.53	203	204	267

**Table 2** Test result of running the GET command
Redis Cache Size	CPU Type	Concurrent Connections	QPS	99.99^th-Percentile Latency (ms)	First 100^th-Percentile Latency (ms)	Last 100^th-Percentile Latency (ms)
8 GB	x86	1000	119,350.25	6	24	27
8 GB	x86	10,000	77,574.7	152	358	365
32 GB	x86	1000	124,650.98	16	17	17
32 GB	x86	10,000	81,991.41	195	196	199

DCS for Redis 3.0 does not support the Arm CPU architecture, so only x86-based instance test results are provided.

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.