TiDB 5.0 GA: A One-Stop HTAP Solution Delivering Speed, Stability, and Simplicity
Transcreator: Caitin Chen; Editor: Tom Dewan
Today, we are proud to announce that TiDB 5.0 has reached general availability (GA). This release marks a significant milestone in our commitment to providing our customers with an open-source, elastic, Hybrid Transactional/Analytical Processing (HTAP) database for mission-critical applications and providing a single and real-time source of truth. Version 5.0 introduces:
- Remarkable improvements in performance and stability. TiDB 5.0 has more powerful OLTP capabilities for mission-critical applications.
- A Massively Parallel Processing (MPP) architecture. This architecture, based on TiDB’s analytical engine, TiFlash, is now available in TiDB. It enables users to perform real-time interactive business intelligence (BI) analytics. It provides a one-stop data service solution for fast-growing businesses and data-driven innovation scenarios and accelerates TiDB’s entry into more large-scale enterprises’ digital scenarios.
- Safer and easier: The Raft Joint Consensus algorithm introduced in TiDB 5.0 improves the system availability during Raft membership change. Data desensitization is also supported to avoid leaking sensitive information. TiDB 5.0 offers multiple data migration and data sharing tools, which facilitate data importing, exporting, and recovering. Enhanced
EXPLAIN ANALYZEstatements help users more efficiently diagnose query performance problems. TiDB 5.0 makes it easier than ever before for enterprises to build and scale applications on TiDB and enables enterprises to build a converged, simplified, and reliable distributed database platform.
High performance with multiple groundbreaking metrics
Compared with version 4.0, TiDB 5.0 has achieved a noteworthy performance boost. By introducing clustered indexes, async commit, and Coprocessor Cache, it has improved the sysbench and TPC-C benchmarks by 20% to 80% in OLTP scenarios. The following are the metrics in some general performance test scenarios:
16 tables, each with 10 million rows of data
TiDB 4.0 vs. TiDB 5.0 for sysbench update non-index benchmarks (higher is better)
TiDB 4.0 vs. TiDB 5.0 for sysbench update index benchmarks (higher is better)
TiDB 4.0 vs. TiDB 5.0 for sysbench read-write benchmarks (higher is better)
TiDB 4.0 vs. TiDB 5.0 for TPC-C benchmarks (higher is better)
Besides, TiDB 5.0 has improved its performance in OLAP scenarios by introducing the TiFlash MPP computing model. For a TPC-H performance test, the TiDB MPP engine’s overall performance is 2 to 3 times that of Greenplum 6.15.0 or Apache Spark 3.1.1. For certain queries, the MPP engine’s performance is even 7 times higher.
- For TPC-H benchmark details, see this report.
TiDB 4.0 vs. TiDB 5.0 for TPC-H benchmarks (lower is better)
In TiDB 5.0, we’ve optimized I/O, network, CPU, and memory resources usage in the TiDB scheduling process, resulting in great improvement in stability. This significantly reduces queries per second (QPS) and query latency jitters caused by resource preemption. In our TPC-C test, the standard deviation value for measuring TPC-C QPS jitter was less than 2%.
See this report.
Standard deviation value for measuring TPC-C QPS jitter
Use TiDB more easily and efficiently
Maintain your cluster more easily
In TiDB 5.0, TiUP checks the environment with a single command line. It offers repair suggestions and automatically repairs environmental problems. We’ve optimized the operation logic so that you can more quickly deploy standard TiDB clusters in the production environment.
In this release, TiUP upgrade is application-unaware. During the upgrade process, the performance jitter is within 10 to 30 seconds.
When you upgrade TiDB, to avoid performance jitter, you can enable the baseline capturing feature to let the system automatically capture and bind the latest execution plan and store it in the system table. After TiDB is upgraded, you can export the bound execution plan and decide whether to delete the binding.
Tune SQL performance more efficiently
TiDB 5.0 supports invisible indexes. When you tune performance or select optimal indexes, you can use SQL statements to set an index to be
Invisible to the optimizer. This avoids performing resource-consuming operations, such as
DROP INDEX and
When you find the root cause of the SQL performance issue and want to force the optimizer to choose a certain query plan, you can use the SQL binding feature to bind the optimized query plan to the SQL statement to be executed. TiDB 5.0 supports SQL binding for data manipulation language (DML) queries, for example,
Enhanced ecosystem tools
TiDB has multiple data migration, data import, and data sharing components, so you can use it in a heterogeneous environment.
Data migration tools are more cloud-native
In TiDB 5.0, it is not only easier but also faster to export and import data on cloud.
The Dumpling data export tool supports using Amazon S3 (and other S3-compatible storage services) as the target storage. This can be used to export data from TiDB and MySQL (including MariaDB and Aurora-MySQL). TiDB Lightning, our data import tool, supports importing data from S3 into TiDB directly. The data could be the output of Dumpling and the snapshot data of AWS Aurora-MySQL. This gives you more options for migrating data to TiDB.
TiDB Lightning optimizes its data import performance. Testing with TiDB Cloud’s AWS T1.standard configurations (or the equivalent) and 1 TB of TPC-C data, the results showed that the speed improved by 40%, from 254 GiB/h to 366 GiB/h.
TiCDC provides integration with Confluent Platform. It uses the Kafka Connectors protocol to replicate TiDB’s data changes to other relational or non-relational databases, such as Kafka, Hadoop, and Oracle. This helps users stream TiDB data to other systems. The solution is verified by Confluent.
TiCDC supports replicating data across multiple TiDB clusters, allowing you to quickly recover backup data from disasters. TiCDC also allows you to aggregate data among multiple TiDB clusters.
Enhanced enterprise-grade features
High availability and fault tolerance
TiDB 5.0 introduces the Raft Joint Consensus algorithm. During Raft membership changes, this algorithm combines the add member and delete member operations into a single operation and sends the operation to all members. This improves the system availability during Raft membership change. During the change process, Raft group members are in an intermediate state. If any modified member fails, the system is still available.
To meet security compliance requirements, TiDB supports desensitizing data, such as IDs and credit card numbers in logs. This avoids leaking sensitive information.
Try us out!
This post only shows a few of highlights in TiDB 5.0. For a full list of features, check out What’s New in TiDB 5.0. If you’re interested, you can download TiDB 5.0 and give it a try. You’re also welcome to join our community on Slack and send us your feedback.
We’d like to give special thanks to the members of our TiDB community — both developers and users — who have contributed to the TiDB ecosystem. Since TiDB 4.0 was released, 538 contributors have submitted 12,513 pull requests to help us improve TiDB and achieve our 5.0 milestone. We have always been fully committed to the open source community and we believe the open community, the open ecosystem and the open minds will continue to enable and empower TiDB to evolve.
Originally published at https://pingcap.com.