Standard Edition - single-replica instances
This topic describes the specifications of Standard Edition single-replica instances of Redis Open-Source Edition. The specifications include memory capacity, maximum connections, internal bandwidth, and reference values for queries per second (QPS).
The single-replica architecture does not ensure data availability or service continuity. Before you select this architecture, make sure you understand the risks. We do not recommend using single-replica instances in a production environment. The Tair (Redis OSS-compatible) Service-Level Agreement (SLA) does not apply to single-replica instances.
Instance specifications
|
Specification name |
Specification code (for API calls) |
CPU cores |
Memory (GB) |
Bandwidth |
Maximum connections |
QPS reference value |
|
1 GB single-replica |
redis.basic.small.default |
2 |
1 |
80 Mbps (10 MB/s) |
10,000 |
80,000 |
|
2 GB single-replica |
redis.basic.mid.default |
2 |
2 |
128 Mbps (16 MB/s) |
10,000 |
80,000 |
|
4 GB single-replica |
redis.basic.stand.default |
2 |
4 |
192 Mbps (24 MB/s) |
20,000 |
80,000 |
|
8 GB single-replica |
redis.basic.large.default |
2 |
8 |
192 Mbps (24 MB/s) |
20,000 |
80,000 |
|
16 GB single-replica |
redis.basic.2xlarge.default |
2 |
16 |
256 Mbps (32 MB/s) |
20,000 |
80,000 |
|
32 GB single-replica |
redis.basic.4xlarge.default |
2 |
32 |
256 Mbps (32 MB/s) |
30,000 |
80,000 |
The maximum connections values above apply to instances compatible with Redis 5.0 or later. For instances compatible with Redis 4.0, the maximum number of connections is 10,000 regardless of specification.
CPU cores
Each instance has 2 CPU cores. One core is reserved for background tasks to maintain service stability. For cluster or read/write splitting instances, one core is reserved per data shard or read-only node.
Bandwidth
Total bandwidth: The bandwidth value represents the total for the instance, summed across all shards or nodes.
Bidirectional: Bandwidth applies equally to upstream and downstream traffic. For example, an 80 Mbps instance has 80 Mbps upstream and 80 Mbps downstream.
Scope: The bandwidth limit for Tair and Redis Open-Source Edition applies to shard nodes and is independent of the network connection type.
To handle burst or planned traffic peaks, adjust the instance bandwidth as needed. See Manually increase the bandwidth of an instance.
For more information, see the Bandwidth FAQ.
Connection calculation rules
The maximum number of new connections per second specifies how many connections can be established within one second. For example, assume that an instance supports up to 10,000 new connections per second and 50,000 concurrent connections, and that the actual number of connections in the nth second after the instance starts is 12,000. In this case, the number of connections in the (n+1)th second can be at most 22,000 (12,000 + 10,000).
Instance creation methods
You can call the CreateInstanceoperation to create a standalone instance, or create a standalone instance on theSubscription (local disk)tab. For more information about how to create an instance in the console, seeStep 1: Create an instance.
Standalone instances can be created only on theSubscription (local disk)tab.
FAQ
My instance's actual bandwidth differs from the spec listed here. Why?
Bandwidth limits for some instance types change after product upgrades. To get the updated bandwidth without extra cost, change the instance configuration and select your current instance type as the target — the system applies the new limits at no additional charge.
Write operations are failing on my cluster instance, but memory isn't full. Why?
Redis distributes keys across shards using a hash algorithm. Large keys can skew this distribution — one shard fills up while others stay empty, causing writes to that shard to fail.
Use the Performance monitoring feature to check memory usage per shard and identify hot shards. See View the performance metrics of nodes in a Tair cluster instance for details.
Does "8proxy" in an instance type code like `redis.logic.sharding.1g.8db.0rodb.8proxy.default` mean there are eight proxy nodes?
No. The 8proxy segment does not represent the number of proxy nodes. Proxy capacity and bandwidth are guaranteed to meet the specs listed in the tables — you don't need to track the actual node count.