Skip to content
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

[Phase 3][Colocation] Use single RPC for joins #4515

Open
ndeodhar opened this issue May 19, 2020 · 1 comment
Open

[Phase 3][Colocation] Use single RPC for joins #4515

ndeodhar opened this issue May 19, 2020 · 1 comment
Labels
area/ysql Yugabyte SQL (YSQL) kind/enhancement This is an enhancement of an existing feature priority/medium Medium priority issue

Comments

@ndeodhar
Copy link
Contributor

ndeodhar commented May 19, 2020

Jira Link: [DB-389](https://yugabyte.atlassian.net/browse/DB-389)
Since colocated tables are stored on the same tablet, we can optimize join queries to use a single RPC to read data instead of multiple, separate RPCs.
This is similar to the optimization that we have done for index scans.

@azapedia
Copy link

azapedia commented Dec 2, 2020

Hi guys, thanks for the great work on YugabyteDB, want to ask if this is already addressed. I have tested the colocated table with simple and complex joins. Seems like the performances in some cases are not far too different. And in some cases, it is worst than a non-colocated table. And do you have a query cache?

@tverona1 tverona1 changed the title [Colocation] Use single RPC for joins [Phase 3][Colocation] Use single RPC for joins May 17, 2022
@yugabyte-ci yugabyte-ci added kind/bug This issue is a bug priority/medium Medium priority issue labels May 17, 2022
@yugabyte-ci yugabyte-ci added kind/enhancement This is an enhancement of an existing feature and removed kind/bug This issue is a bug labels Aug 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ysql Yugabyte SQL (YSQL) kind/enhancement This is an enhancement of an existing feature priority/medium Medium priority issue
Projects
Status: No status
Development

No branches or pull requests

3 participants