The deployment method provided in this guide is ONLY FOR quick start, NOT FOR production or comprehensive functionality and stability testing. • To deploy a self-hosted production cluster, see the production launched from this default image are pre-installed with Docker, Go, Java, Node.js, C/C++, Python, Ruby, Rust, PHP, and tools such as Homebrew, Tailscale, and Nginx. You can use a public Docker image or a Dockerfile Note: The following sections list only the required configuration items of ProxySQL. For a comprehensive list of configurations, see ProxySQL documentation. Option 1: Configure ProxySQL using the Admin

The deployment method provided in this guide is ONLY FOR quick start, NOT FOR production or comprehensive functionality and stability testing. • To deploy a self-hosted production cluster, see the production launched from this default image are pre-installed with Docker, Go, Java, Node.js, C/C++, Python, Ruby, Rust, PHP, and tools such as Homebrew, Tailscale, and Nginx. You can use a public Docker image or a Dockerfile Note: The following sections list only the required configuration items of ProxySQL. For a comprehensive list of configurations, see ProxySQL documentation. Option 1: Configure ProxySQL using the Admin

The deployment method provided in this guide is ONLY FOR quick start, NOT FOR production or comprehensive functionality and stability testing. • To deploy a self-hosted production cluster, see the production launched from this default image are pre-installed with Docker, Go, Java, Node.js, C/C++, Python, Ruby, Rust, PHP, and tools such as Homebrew, Tailscale, and Nginx. You can use a public Docker image or a Dockerfile Note: The following sections list only the required configuration items of ProxySQL. For a comprehensive list of configurations, see ProxySQL documentation. Option 1: Configure ProxySQL using the Admin

The deployment method provided in this guide is ONLY FOR quick start, NOT FOR production or comprehensive functionality and stability testing. • To deploy a self-hosted production cluster, see the production launched from this default image are pre-installed with Docker, Go, Java, Node.js, C/C++, Python, Ruby, Rust, PHP, and tools such as Homebrew, Tailscale, and Nginx. You can use a public Docker image or a Dockerfile Note: The following sections list only the required configuration items of ProxySQL. For a comprehensive list of configurations, see ProxySQL documentation. Option 1: Configure ProxySQL using the Admin

The deployment method provided in this guide is ONLY FOR quick start, NOT FOR production or comprehensive functionality and stability testing. • To deploy a self-hosted production cluster, see the production launched from this default image are pre-installed with Docker, Go, Java, Node.js, C/C++, Python, Ruby, Rust, PHP, and tools such as Homebrew, Tailscale, and Nginx. You can use a public Docker image or a Dockerfile Note: The following sections list only the required configuration items of ProxySQL. For a comprehensive list of configurations, see ProxySQL documentation. Option 1: Configure ProxySQL using the Admin

Shoulders of Giants • Contribute to and enjoy the benefit from the open source community • rust-prometheus, rust-grpc, raft-rs • go-mysql, go-hbase • etcd, rocksdb The TiDB Community •Stars •TiDB: 12

The deployment method provided in this guide is ONLY FOR quick start, NOT FOR production or comprehensive functionality and stability testing. • To deploy a self-hosted production cluster, see the production launched from this default image are pre-installed with Docker, Go, Java, Node.js, C/C++, Python, Ruby, Rust, PHP, and tools such as Homebrew, Tailscale, and Nginx. You can use a public Docker image or a Dockerfile Note: The following sections list only the required configuration items of ProxySQL. For a comprehensive list of configurations, see ProxySQL documentation. Option 1: Configure ProxySQL using the Admin

The deployment method provided in this guide is ONLY FOR quick start, NOT FOR production or comprehensive functionality and stability testing. • To deploy a self-hosted production cluster, see the production launched from this default image are pre-installed with Docker, Go, Java, Node.js, C/C++, Python, Ruby, Rust, PHP, and tools such as Homebrew, Tailscale, and Nginx. You can use a public Docker image or a Dockerfile Note: The following sections list only the required configuration items of ProxySQL. For a comprehensive list of configurations, see ProxySQL documentation. Option 1: Configure ProxySQL using the Admin

30 Request_ 4 40 Request ID CPU Usage 40 30 20 10 1 2 3 4 CPU Profiling By SQL Request ● rust-demo ● go-demo TopSQL: SQL Tag - Digest select id from t where a=1; select id from t where a=2;

of almost all stages of a SQL execution, from parsing to returning results, and is relatively comprehensive (you can query and analyze the slow log in TiDB Dashboard in an intuitive way). • By executing that in MySQL or InnoDB. In InnoDB, only a small number of pages are sampled, while in TiDB a comprehensive set of statistics is completely rebuilt. Scripts that were written for MySQL may naively expect server, using a cluster with a single Pump and a single Drainer. As we’ve seen, TiDB Binlog is a comprehensive platform for capturing and processing changes to a TiDB cluster. In a more robust development