Skip to content

Conversation

@xpineal
Copy link

@xpineal xpineal commented Feb 10, 2022

At the beginning of client start, there is no table region info in cache.
If there are many go routine to access a table at same time, they will miss cache and send request package to get table region info.
In this case, too many duplicated requests should be avoid.

At the beginning of client start, there is no table region info in cache.
If there are many go routine to access a table at same time, they will miss cache and send request package to get table region info.
In this case, too many duplicated requests should be avoid.
@dethi
Copy link
Collaborator

dethi commented Feb 10, 2022

This looks similar to #164, not in the implementation but in what it tries to do.

@tsuna
Copy link
Owner

tsuna commented Dec 12, 2023

Discussed this with @dethi today and after looking at data on our clusters with @aaronbee we decided to add an option to the client to perform a cache warm up during initialization by preloading all entries from meta for tables of interest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants