tencent cloud

TXRocks is a transactional storage engine developed by Tencent's TXSQL team based on RocksDB. It saves more storage space and has a lower write amplification.

Product Overview

By leveraging the LSM tree storage structure of RocksDB, the TXRocks transactional storage engine not only reduces wastes caused by InnoDB's half-full pages and fragments, but also uses the compact storage format. Therefore, it has a performance comparable to that of InnoDB but requires only a half or even smaller storage space. It is more suitable for businesses with a large data volume and high requirements for the transactional read/write performance.

Prerequisites

The database version must be MySQL 5.7 or 8.0 on a two-node architecture.

Purchasing TencentDB for MySQL Instance (with RocksDB Engine)

You can select RocksDB as the engine when purchasing an instance on the TencentDB for MySQL purchase page. For more information on other parameters, see Creating MySQL Instance.

Note：

RocksDB is a key-value storage engine, with efficient writing and high compression. Currently, only TencentDB for MySQL 5.7 and 8.0 instances can use the RocksDB engine.

Creating RocksDB Table

If RocksDB is selected as the default engine during instance creation, it will be the default engine used for table creation. You can run the following command to view the default engine:

show variables like '%default_storage_engine%';

If the default engine is RocksDB, you cannot specify a storage engine in table creation statements:

After a table is created, its data will be stored in RocksDB and can be used in the same way as in InnoDB.

Engine Feature Limits

TXRocks has certain limits on engine features as detailed below:

Parameter Description

Note：

When creating a TencentDB for MySQL instance, you can select RocksDB as the default storage engine. You can also customize the parameter template to suit your needs by following the parameter descriptions below.

MySQL 5.7 parameter list

MySQL 8.0 parameter list

RocksDB Monitoring Metrics

RocksDB monitoring metrics are as listed below: