TXRocks is a transactional storage engine developed by Tencent's TXSQL team based on RocksDB, a very popular high-performance persistent key-value (KV) store.
Compared with the B+tree structure used by InnoDB, the LSM tree structure adopted by TXRocks uses much less storage space. InnoDB's B+tree split often results in half-full pages, idle pages, and space waste; therefore, InnoDB has a lower effective page utilization. The size of TXRocks SST files is generally set to dozens or hundreds of MB or a greater value. Therefore, TXRocks has much fewer wastes caused by 4K alignment. Although an SST file is divided into blocks, those blocks don't need to be aligned. In addition, TXRocks SST files use prefix compression, so that only one record will be generated for data records with the same prefix. SST files at different levels can adopt different compression algorithms, further reducing the storage space overheads. Generally, the storage space usage can be reduced by 50%.
You can sync InnoDB data to RocksDB through DTS to improve the write performance and save the storage space.
Note:Data Transmission Service (DTS) is a data transmission service that integrates such features as data migration, sync, and subscription, helping you migrate your databases without interrupting your business and build a high-availability database architecture for remote disaster recovery through real-time sync channels. Its data subscription feature grants you real-time access to incrementally updated data in your TencentDB instance, so that you can consume such data based on your business needs.
Configuration Item | Description |
---|---|
Source Instance Type | Select the source database type, which cannot be changed after purchase. Here, select MySQL. |
Source Instance Region | Select the source database region. If the source database is a self-built one, select a region nearest to it. |
Target Instance Type | Select the target database type, which cannot be changed after purchase. Here, select MySQL. |
Target Instance Region | Select the target database region. |
Specification | Select the specification of the migration linkage according to your business conditions. For the performance and billing details of different specifications, see Billing Overview. |
Note:If the connectivity test fails, troubleshoot and fix the problem as prompted and as instructed in Database Connection Check and try again.
Note:
- If you want to use a tool such as gh-ost and pt-osc to perform online DDL operations on a table during migration, you must select the entire database (or entire instance) where the table resides rather than only the table as the migration object; otherwise, the temporary table data generated by online DDL changes cannot be migrated to the target database.
- If you want to rename a table (for example, rename table A table B) during migration, you must select the entire database (or entire instance) where table A resides rather than only table A as the migration object; otherwise, the system will report an error.
Configuration Item | Description |
---|---|
Migration Type | Select a type based on your scenario.
|
Migration Object |
|
Specified objects | Select the objects to be migrated in Source Database Object and move them to the Selected Object box. |
Migrate Account | Select this feature if you want to migrate the account information of the source database. |
Was this page helpful?