platform Reporting Databases App BI Console Ad hoc Data Platform - What You Think It Is OLTP DBs App Data Warehouse / Data Lake ETL Analytical DBs Reporting BI Console Ad hoc Data Platform point / short access ○ Row format for OLTP ○ Columnar format for OLAP ● Workload Interference ○ A single large analytical query might cause disaster for your OLTP workload Fundamental Conflicts ● Use Use different types of databases ○ For live and fast data, use an OLTP specialized database or NoSQL ○ For historical data, use Hadoop / analytical database ● Offload data via the ETL process into your

动态扩展 分布式事务 HTAP 真正⾦融级⾼可⽤ 适⽤场景 适⽤场景 对数据⼀致性及⾼可靠、系统⾼可⽤、可扩展性、容灾要求较⾼的⾦融⾏业属性的场景 对存储容量、可扩展性、并发要求较⾼的海量数据及⾼并发的 OLTP 场景 Real-time HTAP 场景 数据汇聚、⼆次加⼯处理的场景 真正⾦融级⾼可⽤ UCloud 云上 云上 TiDB 架构⽰意图 架构⽰意图 TiDB TiDB Serverless ⽬录 failover)，⽆需⼈⼯介⼊。 产品优势 分布式NewSQL数据库 TiDB Copyright © 2012-2021 UCloud 优刻得 13/120 适⽤场景 适⽤场景 为⽤⼾提供⼀站式 OLTP (Online Transactional Processing)、OLAP (Online Analytical Processing)、HTAP 解决⽅案。TiDB 适合⾼可⽤、强⼀致要求较⾼、数据规模较⼤等各种应⽤ 现故障时系统可⾃动进⾏切换，确保系统的 RTO <= 30s 及 RPO = 0。 对存储容量、可扩展性、并发要求较⾼的海量数据及⾼并发的 对存储容量、可扩展性、并发要求较⾼的海量数据及⾼并发的 OLTP 场景 场景 随着业务的⾼速发展，数据呈现爆炸性的增⻓，传统的单机数据库⽆法满⾜因数据爆炸性的增⻓对数据库的容量要求，可⾏⽅案是采⽤分库分表的中间件产品或者 NewSQL 数据库替代、 采⽤⾼端的存储设备等，其中性价⽐最⼤的是

Analytical Processing) 数据库，结合了传统的 RDBMS 和 NoSQL 的最佳特性。 TiDB 兼容 MySQL，支持无限的水平扩展，具备强一致性和高可用性。TiDB 的目标是为 OLTP (Online Transactional Processing) 和 OLAP (Online Analytical Processing) 场景提供一站式的解决方案。 TiDB 具备如下核心特性： 作为典型的 OLTP 行存数据库，同时兼具强大的 OLAP 性能，配合 TiSpark，可提供一站式 HTAP 解决方案，一份存储同时处理 OLTP & OLAP，无需传统繁琐的 ETL 过程。 云原生 SQL 数据库 TiDB 是为云而设计的数据库，同 Kubernetes 深度耦合，支持公有云、私有云和混合云，使部署、配置和 维护变得十分简单。 TiDB 的设计目标是 100% 的 OLTP 场景和 Analytical Processing) 数据库，结合了传统的 RDBMS 和 NoSQL 的最佳特性。 TiDB 兼容 MySQL，支持无限的水平扩展，具备强一致性和高可用性。TiDB 的目标是为 OLTP (Online Transactional Processing) 和 OLAP (Online Analytical Processing) 场景提供一站式的解决方案。 TiDB 具备如下核心特性：

· · · · · · · · · · · · · · · · · · · · · · · · · · 1771 11.1.8 Performance Tuning Practices for OLTP Scenarios· · · · · · · · · · · · · · · · · · 1796 11.1.9 TiFlash Performance Analysis and Tuning · · · · · · · · · · · · · · · · · · · · · · · · · · · 6726 17.11.3 Online Transaction Processing (OLTP) · · · · · · · · · · · · · · · · · · · · · · · · · · · 6726 17.11.4 Out of Memory (OOM)· · · · · avail- ability. The goal of TiDB is to provide users with a one-stop database solution that covers OLTP (Online Transactional Processing), OLAP (Online Analytical Processing), and HTAP services. TiDB is

· · · · · · · · · · · · · · · · · · · · · · · · · · 1473 11.1.8 Performance Tuning Practices for OLTP Scenarios· · · · · · · · · · · · · · · · · · 1498 11.1.9 TiFlash Performance Analysis and Tuning avail- ability. The goal of TiDB is to provide users with a one-stop database solution that covers OLTP (Online Transactional Processing), OLAP (Online Analytical Processing), and HTAP services. TiDB is by caching more �→ execution plans in memory, decreasing overall SQL execution time. It �→ improves OLTP performance and throughput while providing better �→ control over memory usage and enhancing database

· · · · · · · · · · · · · · · · · · · · · · · · · · 1360 11.1.3 Performance Tuning Practices for OLTP Scenarios· · · · · · · · · · · · · · · · · · 1385 11.1.4 TiFlash Performance Analysis and Tuning avail- ability. The goal of TiDB is to provide users with a one-stop database solution that covers OLTP (Online Transactional Processing), OLAP (Online Analytical Processing), and HTAP services. TiDB is information, see documentation. • Enhance SQL execution plan binding #55280 #55343 @time-and-fate In OLTP scenarios, the optimal execution plan for most SQL statements is fixed. Imple- menting SQL execution

· · · · · · · · · · · · · · · · · · · · · · · · · · 1351 11.1.3 Performance Tuning Practices for OLTP Scenarios· · · · · · · · · · · · · · · · · · 1374 11.1.4 TiFlash Performance Analysis and Tuning avail- ability. The goal of TiDB is to provide users with a one-stop database solution that covers OLTP (Online Transactional Processing), OLAP (Online Analytical Processing), and HTAP services. TiDB is basic knowledge about TiKV, a row- based storage engine for TiDB Online Transactional Processing (OLTP), and TiFlash, a columnar storage engine for TiDB Online Analytical Processing (OLAP). • Storage

· · · · · · · · · · · · · · · · · · · · · · · · · · 1354 11.1.3 Performance Tuning Practices for OLTP Scenarios· · · · · · · · · · · · · · · · · · 1377 11.1.4 TiFlash Performance Analysis and Tuning avail- ability. The goal of TiDB is to provide users with a one-stop database solution that covers OLTP (Online Transactional Processing), OLAP (Online Analytical Processing), and HTAP services. TiDB is basic knowledge about TiKV, a row- based storage engine for TiDB Online Transactional Processing (OLTP), and TiFlash, a columnar storage engine for TiDB Online Analytical Processing (OLAP). • Storage

com/tidbslack/ Compare Why Aurora? ● Amazon Aurora is popular ● Amazon Aurora is designed for OLTP workload ● Amazon Aurora is still using the MySQL code base ● It would be cool to do some lightweight complex to deploy than standalone MySQL TiDB Pros & Cons ● High concurrent / large data volume / OLTP application ○ Data volume is growing rapidly and is soon to exceed the capacity of a single machine --mysql-host=123.123.123.123 --mysql-user=root --mysql-port=4000 --mysql-db=sbtest --db-driver=mysql oltp_common prepare --tables=16 --table-size=10000000 --auto-inc=false Thread TiDB 3.0 Amazon Aurora