distributed-cache-service/umn/source/introduction/dcs_instance_specifications.rst

original_name

en-us_topic_0054235835.html

DCS Instance Specifications

For each single-node DCS Redis instance, the available memory is less than the total memory because some memory is reserved for system overhead, as shown in Table 1 <en-us_topic_0054235835__table2399016819>.

Table 1 Specifications of single-node DCS Redis 3.0 instances

Total Memory (GB)	Available Memory (GB)	Maximum Connections Allowed (Count)	Assured/Maximum Bandwidth (Mbit/s)
2	1.5	10,000	42/512
4	3.2	10,000	64/1,536
8	6.8	10,000	64/1,536
16	13.6	10,000	85/3,072
32	27.2	10,000	85/3,072
64	58.2	12,000	128/5,120

For each master/standby DCS Redis instance, the available memory is less than that of a single-node DCS Redis instance because some memory is reserved for data persistence, as shown in Table 2 <en-us_topic_0054235835__table1540218117813>. The available memory of a master/standby instance can be adjusted to support background tasks such as data persistence and master/standby synchronization.

Table 2 Specifications of master/standby DCS Redis 3.0 instances

Total Memory (GB)	Available Memory (GB)	Maximum Connections Allowed (Count)	Assured/Maximum Bandwidth (Mbit/s)
2	1.5	10,000	42/512
4	3.2	10,000	64/1,536
8	6.4	10,000	64/1,536
16	12.8	10,000	85/3,072
32	25.6	10,000	85/3,072
64	51.2	12,000	128/5,120

In addition to larger memory, Proxy Cluster instances feature more connections allowed and higher bandwidth allowed than single-node and master/standby instances.

Table 3 Specifications of Proxy Cluster DCS Redis 3.0 instances

Total Memory (GB)	Available Memory (GB)	Maximum Connections Allowed	Assured/Maximum Bandwidth (Mbit/s)
64	64	90,000	600/5,120
128	128	180,000	600/5,120
256	256	240,000	600/5,120
512	512	480,000	600/5,120