feat: introduce information schema provider cache #3208
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
Each time invoking the
self.system_catalog.table(catalog, schema, table_name)
, thesystem_catalog
makes a newInformationSchemaProvider
, which is time-consuming.If we execute the
SELECT * FROM information_schema. tables;
, eachself.system_catalog.table(catalog, schema, table_name)
invoking will take ~30ms, resulting in query will spend ~500ms. The key problem here:BTW, I checked the behavior on the cloud, and the
information_schema
doesn't work.Checklist
Refer to a related PR or issue link (optional)