Packaged Installs 31 Next Steps 31 Installing the Cassandra Tarball Distribution 31 About Cassandra Binary Installations 32 Installing JNA 32 Next Steps 32 Initializing a Cassandra Cluster on Amazon EC2 90 Monitoring and Adjusting Cache Performance 91 Tuning Cassandra 91 Tuning the Cache 92 How Caching Works 92 Configuring the Column Family Key Cache 92 Configuring the Column Family Row Cache 92 quickest way to get going on a single node with Cassandra is to install the DataStax Community Edition binary tarball packages. This allows you to install everything in a single location (such as your home directory)

slow query log (including the configuration of seconds it requires to execute a query), and the binary log. During the configuration process, click Next to proceed to the next step or Back to return of seconds it requires to execute a query), and the binary log. The Advanced Options step enables you to set the unique server ID required when binary logging is enabled in a replication topology. • MySQL this step. MySQL 8.0 connectors and community drivers that use libmysqlclient 8.0 now support the caching_sha2_password default authentication plugin. However, if you are unable to update your clients and

plan cache. Compared with session-level plan �→ cache, this feature reduces SQL compilation time by caching more �→ execution plans in memory, decreasing overall SQL execution time. It �→ improves OLTP performance instance-level execution plan cache offers the following advantages: • Eliminates redundancy, caching more execution plans with the same memory consumption. • Allocates a fixed-size memory on the instance limiting memory usage more effec- tively. In v8.4.0, instance-level execution plan cache only supports caching query execution plans and is disabled by default. You can enable this feature using tidb_enable_instance

plan cache. Compared with session-level plan �→ cache, this feature reduces SQL compilation time by caching more �→ execution plans in memory, decreasing overall SQL execution time. It �→ improves OLTP performance instance-level execution plan cache offers the following advantages: • Eliminates redundancy, caching more execution plans with the same memory consumption. • Allocates a fixed-size memory on the instance limiting memory usage more effec- tively. In v8.4.0, instance-level execution plan cache only supports caching query execution plans and is disabled by default. You can enable this feature using tidb_enable_instance

end-to-end restore speed improving by approximately 1.5 to 3 �→ times. Enhance the stability of caching the schema information when there is a �→ massive number of tables (experimental) SaaS pingcap.com/tidb/v8.0/system- �→ variables#tidb_schema_cache_size-new-in-v800">schema information �→ caching system, incorporating a lazy-loading Least Recently Used �→ (LRU) cache for table metadata and TSO feature is enabled. For more information, see documentation. 2.2.1.3 Reliability • Support caching required schema information according to the LRU algorithm to re- duce memory consumption on the

load, and �→ restore operations when used for data loading. Enhance the stability of caching the schema information when there is a �→ massive number of tables (experimental, introduced in pingcap.com/tidb/v8.1/system- �→ variables#tidb_schema_cache_size-new-in-v800">schema information �→ caching system, which provides a cache strategy based on the �→ Least Recently Used (LRU) algorithm for monitoring metric for DR Auto-Sync does not show any data #7974 @lhy1024 • Fix the issue that checking binary versions might cause PD panic #7978 @JmPotato • Fix the type conversion error that occurs when

scattering read hotspots. For more information, see documentation. • Enhance the capability of caching execution plans for non-prepared statements (exper- imental) #36598 @qw4990 TiDB v7.0.0 introduces improve the load capacity of concurrent OLTP. In v7.1.0, TiDB enhances this feature and supports caching more SQL statements. To improve memory utilization, TiDB v7.1.0 merges the cache pools of non-prepared result to a TiDB table specified by INSERT INTO for further analysis, which takes effect as result caching (that is, result materialization). In v7.1.0, this feature is generally available. During the execution

#54074 @ywqzzy 57 • Improve the query performance for certain system tables when schema information caching is enabled #50305 @tangenta • Optimize error messages for conflicting keys when adding unique indexes authentication (RBAC) Y Y Y Y Y Y Y Y Y Y Y Certificate-based authentication Y Y Y Y Y Y Y Y Y Y Y caching_sha2_password authentication Y Y Y Y Y Y Y Y Y Y N tidb_sm3_password authentication Y Y Y Y Y Y GIS/GEOMETRY) functions, data types and indexes #6347 • Character sets other than ascii, latin1, binary, utf8, utf8mb4, and gbk. • Optimizer trace • XML Functions • X-Protocol #1109 • Column-level privileges

cache most execution plans to save execution overhead and reduce latency. Currently, execution plan caching has some limitations on SQL. Execution plans of some SQL statements cannot be cached. It is difficult authentication (RBAC) Y Y Y Y Y Y Y Y Y Y Certificate-based authentication Y Y Y Y Y Y Y Y Y Y caching_sha2_password authentication Y Y Y Y Y Y Y Y Y N tidb_sm3_password authentication Y Y Y Y Y N N GIS/GEOMETRY) functions, data types and indexes #6347 • Character sets other than ascii, latin1, binary, utf8, utf8mb4, and gbk. • Optimizer trace • XML Functions • X-Protocol #1109 • Column-level privileges

available re- sources. 2.2.3 Offline package changes Starting from v7.6.0, the TiDB-community-server binary-package now includes tiproxy �→ -{version}-linux-{arch}.tar.gz, which is the installation package support automatic retries of optimistic transactions. 63 2.2.5 Improvements • TiDB • When a non-binary collation is set and the query includes LIKE, the optimizer generates an IndexRangeScan to improve operations now trigger maintenance updates of statistics #47354 @hi-rustin • TiDB supports building binary files that meet the requirements of Federal Infor- mation Processing Standards (FIPS) #47948 @tiancaiamao