Help Center> Distributed Message Service> Service Overview> Kafka Premium Instances and Advanced Queues> Specifications
Updated on 2022-02-24 GMT+08:00
View PDF

Specifications

Advanced Queue Specifications

The network, storage, and computing resources of advanced queues are managed by DMS. The resources allocated to each queue should be capable of meeting the concurrency and storage requirements of most services. If you have higher concurrency requirements, submit a service ticket for technical support.

To occupy isolated network, storage, and computing resources, use Kafka premium instances instead.

Kafka Premium Instance Specifications

Kafka premium instances are compatible with open-source Kafka 1.1.0. The instance specifications are classified based on bandwidth, including 100 MB/s, 300 MB/s, 600 MB/s, and 1200 MB/s.

Table 1 TPS and maximum number of partitions supported by different instance specifications

Bandwidth

I/O Type

TPS (High-Throughput)

TPS (Synchronous Replication)

Maximum Partitions

100MB/s

High I/O

100,000

60,000

300

Ultra-high I/O

100,000

80,000

300

300MB/s

High I/O

300,000

150,000

900

Ultra-high I/O

300,000

200,000

900

600MB/s

Ultra-high I/O

600,000

300,000

1800

1200MB/s

Ultra-high I/O

1.2 million

400,000

1800

Bandwidth Selection

The bandwidth of a Kafka instance refers to the maximum read or write bandwidth. You are advised to select a bandwidth 30% higher than what is required.

  • 100MB/s

    Recommended for up to 3,000 client connections, 60 consumer groups, and 70 MB/s of service traffic.

  • 300MB/s

    Recommended for up to 10,000 client connections, 300 consumer groups, and 210 MB/s of service traffic.

  • 600MB/s

    Recommended for up to 20,000 client connections, 600 consumer groups, and 420 MB/s of service traffic.

  • 1200MB/s

    Recommended for up to 20,000 client connections, 600 consumer groups, and 840 MB/s of service traffic.

Storage Space Selection

Kafka premium instances support storage with 1 to 3 replicas. The storage space is space consumed by all replicas. When creating an instance, specify its storage space based on the expected service message size and the number of replicas.

For example, if the estimated message size is 100 GB, the disk capacity must be at least: 100 GB x Number of replicas + 100 GB (reserved).

The storage space can be expanded as your service grows.