Release Notes

Product Introduction

Overview

Scenarios

Product Architecture

Instance Types

Compatibility Notes

Kernel Features

Kernel Overview

Kernel Version Release Notes

Functionality Features

Performance Features

Billing

Billing Overview

Purchase Method

Pricing Details

Renewal

Overdue Payments

Refund

Getting Started

Creating an Instance

Connect to Instances

User Guide

Data Migration

Data Subscription

Instance Management

Configuration Change

Parameter Configuration

Account Management

Security Group

Backup and Restoration

Database Auditing

Tag Management

Use Cases

Technical Evolution and Usage Practices of Online DDL

Lock Mechanism Analysis and Troubleshooting Practices

Data Intelligent Scheduling and Related Practices for Performance Optimization

TDSQL Boundless Selection Guide and Practical Tutorial

Developer Guide

Developer Guide (MySQL Compatibility Mode)

Developer Guide (HBase Compatibility Mode)

Performance Tuning

Performance Tuning Overview

SQL Tuning

DDL Tuning

Performance White Paper

Performance Overview

TPC-C Test

Sysbench Test

API Documentation

History

Introduction

API Category

Making API Requests

Instance APIs

Security Group APIs

Task APIs

Backup APIs

Rollback APIs

Parameter APIs

Database APIs

Data Types

Error Codes

General Reference

System Architecture

SQL Reference

Database Parameter Description

TPC-H benchmark data model reference

Error Code Information

Security and Compliance

FAQs

Agreements

Service Level Agreement

Data Processing And Security Agreement

Glossary

Binlog Subscription

PDF

Modo Foco

Tamanho da Fonte

Última atualização: 2026-03-20 18:00:39

TDSQL Boundless supports real-time data synchronization to target databases or third-party platforms by subscribing to MySQL-compatible Binlog events. It is suitable for scenarios such as multi-active across cloud and on-premises environments, cross-region disaster recovery, cross-border synchronization, and real-time data warehousing. The Binlog subscription feature has been stably running in multiple Tencent core businesses for over a year, covering scenarios including e-commerce marketing, big data scheduling, content moderation, and ad delivery. TDSQL Boundless generates Binlog in a format consistent with MySQL to ensure compatibility with the MySQL community's Binlog subscription ecosystem, such as Canal, Flink, and Kafka (which can be delivered via DTS). The Binlog is produced by converting asynchronous log streams generated through the Raft consensus protocol. This design enables Binlog with minimal overhead on write operations.
Performance Stress Test
Sysbench benchmark test
Test Item
Test Value
Total Data Volume
10 million × 10 tables
Testing Model
sysbench update non index
Binlog subscription node throughput
10.5w QPS
Resource Specification
32C 64G
CPU usage
4C
Memory usage
8.4GB
72-hour stability test
Test Item
Test Configuration
Instance Specifications
3MC (4C8G) + 15HyperNode (16C32G) + 1Binlog subscription node (48C96G)
Client pressure
15 tables, 15 concurrency, totaling 50,000 QPS insert
Duration
72 hours
Synchronization delay
stably maintained within 10s
Wide-table scenario optimization
Wide-table scenario (average row length 1.5KB), client-side pressure 50,000 QPS, replay delay maintaining within 10s.
Table structure as follows:
CREATE TABLE `sbtest1` (
  `id` bigint NOT NULL,
  `uid` bigint NOT NULL,
  `phase` int NOT NULL,
  `status` int NOT NULL,
  `detail` varchar(1024) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `createdTime` datetime NOT NULL,
  `lastModTime` datetime NOT NULL,
  `business` varchar(128) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL,
  `materialId` varchar(128) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL,
  `materialType` int NOT NULL,
  `reviewDataId` bigint NOT NULL,
  `deleteStatus` int NOT NULL,
  `traceId` varchar(128) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `reviewDataLogDetail` mediumblob,
  `physicalFinger` varchar(128) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `originalFinger` varchar(128) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `originalResourceId` varchar(128) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `parentTraceId` varchar(128) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `grandParentId` varchar(128) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `parentId` varchar(128) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  PRIMARY KEY (`id`),
  KEY `idx_materialId` (`materialId`),
  KEY `idx_uid` (`uid`),
  KEY `idx_reviewDataId` (`reviewDataId`),
  KEY `idx_createdTime` (`createdTime`),
  KEY `idx_phase` (`phase`),
  KEY `idx_status` (`status`),
  KEY `idx_parentId` (`parentId`)
) ENGINE=ROCKSDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci ROW_FORMAT=COMPRESSED KEY_BLOCK_SIZE=8
Large transaction scenario optimization
In scenarios involving batch processing or regularly handling large transactions, it is recommended to appropriately adjust the following parameters to enhance performance. 
-- Enhance large transaction processing capability
wait_flush_binlog_cache_max_size = 100MB
﻿
-- Optimize memory usage
tdstore_block_cache_size = 300MB
Subscription Limitation
When you use Binlog to subscribe to TDSQL Boundless data changes, please note the following restrictions and currently unsupported scenarios.
Compatibility issues
Only database instances with kernel version 19.2.0 and above support enabling Binlog subscription.
Currently, generating Binlog for FUNCTION, PROCEDURE, and TRIGGER operations is not supported.
Database instances with kernel versions below 20.0.0 will automatically disable the CREATE TABLE ... AS SELECT ... syntax after Binlog is enabled. To restore it, contact technical support to disable the synchronization feature and restart the instance.
Database instances with kernel versions below 21.0.0 do not support generating Binlog for VIEW  operations.
Feature Limitations
Only subscribing to logs via the MySQL Binlog protocol is supported; downloading Binlog files independently is not currently supported.
A single database instance can create up to 5 Binlog subscription tasks.
Billing Mode
Detailed billing information please see Billing Overview.
Operation Instructions
For enabling and disabling the Binlog subscription feature for TDSQL Boundless instances, refer to Binlog Subscription.

Ajuda e Suporte

Esta página foi útil?

Você também pode entrar em contato com a Equipe de vendas ou Enviar um tíquete em caso de ajuda.

comentários

Test Item	Test Value
Total Data Volume	10 million × 10 tables
Testing Model	sysbench update non index
Binlog subscription node throughput	10.5w QPS
Resource Specification	32C 64G
CPU usage	4C
Memory usage	8.4GB

Test Item	Test Configuration
Instance Specifications	3MC (4C8G) + 15HyperNode (16C32G) + 1Binlog subscription node (48C96G)
Client pressure	15 tables, 15 concurrency, totaling 50,000 QPS insert
Duration	72 hours
Synchronization delay	stably maintained within 10s

tencent cloud

TDSQL Boundless

Binlog Subscription

Performance Stress Test

Sysbench benchmark test

72-hour stability test

Wide-table scenario optimization

Large transaction scenario optimization

Subscription Limitation

Compatibility issues

Feature Limitations

Billing Mode

Operation Instructions

Ajuda e Suporte