-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[#7535] YSQL: Use geo-location (tablespace) to cost index scans
Summary: This introduces functionality to select an index placement to scan from based on their placements encoded in a tablespace. We cost a tablespace by first costing each of its placement options and pessimistically choosing the worst of the placement options. Each placement option is scored based on a prefix comparison with our current node placement and assigns costs appropriately. Here are the current cost assignments: The placement is zone-local (cloud, region and zone match): 9.4 The placement is region-local (cloud and region match): 9.5 The placement is cloud-local (cloud matches): 10.0 The placement is not-local (nothing matches): 10.0 The main motivation behind these costs is to keep the not-local scenario more expensive than the default cost that one obtains without considering tablespaces (10.0). Test Plan: ybd --scb --sj org.yb.pgsql.TestPgRegressTablespaces#testPgRegressTablespaces Reviewers: rskannan, dmitry, dsrinivasan, mihnea Reviewed By: mihnea Subscribers: jason, zyu, yql Differential Revision: https://phabricator.dev.yugabyte.com/D10982
- Loading branch information
Tanuj Nayak
committed
May 25, 2021
1 parent
2ca94c4
commit bebd181
Showing
17 changed files
with
476 additions
and
22 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.