From 063e85c4ffad4cb3d0592698ca1eca9a16e41955 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Fri, 22 Nov 2024 18:05:47 +0800 Subject: [PATCH] schema cache ga (#19401) --- schema-cache.md | 4 ---- system-variables.md | 4 ---- 2 files changed, 8 deletions(-) diff --git a/schema-cache.md b/schema-cache.md index b25cf2a45c010..da45dab0930ad 100644 --- a/schema-cache.md +++ b/schema-cache.md @@ -7,10 +7,6 @@ summary: TiDB adopts an LRU-based (Least Recently Used) caching mechanism for sc In some multi-tenant scenarios, there might be hundreds of thousands or even millions of databases and tables. Loading the schema information of all these databases and tables into memory would not only consume a large amount of memory but also degrade access performance. To address this issue, TiDB introduces a schema caching mechanism similar to LRU (Least Recently Used). Only the schema information of the most recently accessed databases and tables is cached in memory. -> **Warning:** -> -> This feature is currently an experimental feature. It is not recommended that you use it in the production environment. This feature might be changed or removed without prior notice. If you find a bug, you can report an [issue](https://github.com/pingcap/tidb/issues) on GitHub. - ## Configure schema cache You can enable the schema caching feature by configuring the system variable [`tidb_schema_cache_size`](/system-variables.md#tidb_schema_cache_size-new-in-v800). diff --git a/system-variables.md b/system-variables.md index 680e5779ba7d6..3fa693368872f 100644 --- a/system-variables.md +++ b/system-variables.md @@ -5231,10 +5231,6 @@ SHOW WARNINGS; ### tidb_schema_cache_size New in v8.0.0 -> **Warning:** -> -> The feature controlled by this variable is experimental. It is not recommended that you use it in the production environment. This feature might be changed or removed without prior notice. If you find a bug, you can report an [issue](https://github.com/pingcap/tidb/issues) on GitHub. - - Scope: GLOBAL - Persists to cluster: Yes - Applies to hint [SET_VAR](/optimizer-hints.md#set_varvar_namevar_value): No