-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
InfoSchema V2 #50959
Labels
type/enhancement
The issue or PR belongs to an enhancement.
Comments
13 tasks
This was referenced Feb 5, 2024
13 tasks
13 tasks
13 tasks
13 tasks
13 tasks
13 tasks
13 tasks
13 tasks
This was referenced Mar 4, 2024
13 tasks
13 tasks
Merged
13 tasks
This was referenced Jul 31, 2024
hawkingrei
pushed a commit
to hawkingrei/tidb
that referenced
this issue
Aug 1, 2024
…chema v2 full load (pingcap#54879) ref pingcap#50959
13 tasks
13 tasks
13 tasks
13 tasks
13 tasks
13 tasks
13 tasks
13 tasks
This was referenced Aug 22, 2024
13 tasks
13 tasks
13 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Enhancement
When we have millions of tables, the memory footprint for meta data is not negligible.
Some users use TiDB to provide services to their tenant, so there could be a huge amount of tables.
We need to develop a kind of caching mechanism to ensure that even in the extreme cases, the meta data do not cause TiDB OOM.
In the new design, the table.Table will not be persisted in memory, insted, they will be cached.
Development tasks
The text was updated successfully, but these errors were encountered: