tencent cloud

TDSQL Boundless

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
Terms of Service
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

tdstore_user_cf_soft_pending_compaction_bytes_limit

PDF
フォーカスモード
フォントサイズ
最終更新日: 2026-03-27 19:15:05

Feature Description

TDStore uses a Log-Structured Merge-tree (LSM-tree) structure to organize and store data. The LSM-tree organizes data in layers, divided into level 0 through level N. The most recently written data is first flushed to disk in the data files at level 0.Periodically, the LSM-tree initiates a compaction operation to reorganize the stored data, gradually moving data from an upper layer (level i) to the next lower layer (level i+1), thereby maintaining a healthy structure for the LSM-tree. During this process, outdated data versions are cleaned up, which frees up redundant disk space to achieve optimal read and write performance.When the database's write pressure becomes too high, the compaction operation may not be able to keep up with reorganizing the newly written data. As a result, the LSM-tree's structure degrades, and read/write performance decreases. After a certain threshold is reached, TDStore will automatically enter a "write slowdown" mode (by rate-limiting write requests) or even a "write stop" state (by rejecting all write requests). At this point, TDStore's write performance has reached its bottleneck.
tdstore_user_cf_soft_pending_compaction_bytes_limit is used to set the threshold for TDStore to enter the write-throttling status. When the data volume pending compaction in TDStore exceeds this parameter, TDStore will enter the write-throttling status and adaptively limit the rate of all write requests. By reasonably setting tdstore_user_cf_soft_pending_compaction_bytes_limit, you can control the threshold for entering the write-throttling status, optimizing system performance and resource utilization.

Attribute Description

Required
Description
Parameter Type
ULONGLONG
Default Value
274877906944
Value Range
0 ~ 18446744073709551615
Effective Scope
GLOBAL
Restart Required
No

ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック