Transactions and Notifications, which de- scribed Percolator: a Google-internal database for ran- dom access transactional workloads where low laten- cies are not required. Percolator uses a global co-

Memory ● OS ○ Virtual memory ■ each process has its virtual address space ○ Physical memory ■ OS divides physical memory into pages ○ memory mapping ■ page fault, built the virtual-physical mapping talking about when we talk about Memory ● TLB (translation lookaside buffer) ○ A CPU cache for virtual memory to physical addresses mapping ○ Size limited, when cache miss the memory access become slower

· · · · · · · · · · · · · · · · · · · · · · · 771 11.2.1 Deploy and operate TiDB on physical or virtual machines · · · · · · · · · · · 772 11.2.2 Deploy and operate TiDB in Kubernetes · · · · · · · · tables in the mysql schema #1143 #1078 * Support the S3-compatible storage that is based on the virtual-host address- ing mode #10243 * Optimize the format of backupmeta to reduce memory usage #1171 contains NULL values in some cases #23891 – Forbid generating MPP plans when the scan contains virtual columns #23886 – Fix the wrong reuse of PointGet and TableDual in Plan Cache #23187 #23144 #23304

· · · · · · · · · · · · · · · · · · · · · · 1993 13.2.1 Deploy and operate TiDB on physical or virtual machines · · · · · · · · · · · 1994 13.2.2 Deploy and operate TiDB on Kubernetes· · · · · · · · 3/tiproxy-overview">Built-in �→ virtual IP management in TiProxy TiProxy introduces built-in virtual IP management. When configured, it �→ supports automatic virtual IP switching without relying supports built-in virtual IP management #583 @djshow832 Before v8.3.0, when using primary-secondary mode for high availability, TiProxy re- quires an additional component to manage the virtual IP address. Starting

· · · · · · · · · · · · · · · · · · · · · · 2411 13.2.1 Deploy and operate TiDB on physical or virtual machines · · · · · · · · · · · 2411 13.2.2 Deploy and operate TiDB on Kubernetes· · · · · · · · TiDB supports the following logical objects at the same level as table: • View: a view acts as a virtual table, whose schema is defined by the SELECT statement that creates the view. • Sequence: a sequence AUTO_INCREMENT PRIMARY KEY, order_info JSON, created_at DATE AS (JSON_EXTRACT(order_info, '$.created_at')) VIRTUAL ) TTL = `created_at` + INTERVAL 3 month; 4.6.4.2 TTL job For each table with a TTL attribute,

· · · · · · · · · · · · · · · · · · · · · · 2108 13.2.1 Deploy and operate TiDB on physical or virtual machines · · · · · · · · · · · 2108 13.2.2 Deploy and operate TiDB on Kubernetes· · · · · · · · TiDB supports the following logical objects at the same level as table: • View: a view acts as a virtual table, whose schema is defined by the SELECT statement that creates the view. • Sequence: a sequence AUTO_INCREMENT PRIMARY KEY, order_info JSON, created_at DATE AS (JSON_EXTRACT(order_info, '$.created_at')) VIRTUAL ) TTL = `created_at` + INTERVAL 3 month; 4.6.4.2 TTL job For each table with a TTL attribute,

· · · · · · · · · · · · · · · · · · · · · · · 803 11.2.1 Deploy and operate TiDB on physical or virtual machines · · · · · · · · · · · 804 11.2.2 Deploy and operate TiDB in Kubernetes · · · · · · · · line terminators (except \r and \n) #1297 * Support expression index and the index that depends on virtual generated columns #1407 – Dumpling * Support backing up MySQL compatible databases but does not power policy of the cpufreq module is powersave. You need to modify it to performance. If you use a virtual machine or a cloud host, the output is usually Unable to �→ determine current policy, and you do

· · · · · · · · · · · · · · · · · · · · · · · 944 11.2.1 Deploy and operate TiDB on physical or virtual machines · · · · · · · · · · · 944 11.2.2 Deploy and operate TiDB in Kubernetes · · · · · · · · power policy of the cpufreq module is powersave. You need to modify it to performance. If you use a virtual machine or a cloud host, the output is usually Unable to �→ determine current policy, and you do excellent performance across a variety of common �→ server workloads - virtual-guest - Optimize for running inside a �→ virtual guest - virtual-host - Optimize for running KVM guests Current active profile:

· · · · · · · · · · · · · · · · · · · · · · · 830 11.2.1 Deploy and operate TiDB on physical or virtual machines · · · · · · · · · · · 830 11.2.2 Deploy and operate TiDB in Kubernetes · · · · · · · · power policy of the cpufreq module is powersave. You need to modify it to performance. If you use a virtual machine or a cloud host, the output is usually Unable to �→ determine current policy, and you do excellent performance across a variety of common �→ server workloads - virtual-guest - Optimize for running inside a �→ virtual guest - virtual-host - Optimize for running KVM guests Current active profile:

· · · · · · · · · · · · · · · · · · · · · · 1493 13.2.1 Deploy and operate TiDB on physical or virtual machines · · · · · · · · · · · 1493 13.2.2 Deploy and operate TiDB on Kubernetes· · · · · · · · TiDB supports the following logical objects at the same level as table: • View: a view acts as a virtual table, whose schema is defined by the SELECT statement that creates the view. • Sequence: a sequence document describes how to use views in TiDB. 4.7.5.1 Overview TiDB supports views. A view acts as a virtual table, whose schema is defined by the SELECT statement that creates the view. • You can create views