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

workload: inject stats for workload init tpcc --data-loader IMPORT #64580

Open
rytaft opened this issue May 3, 2021 · 1 comment
Open

workload: inject stats for workload init tpcc --data-loader IMPORT #64580

rytaft opened this issue May 3, 2021 · 1 comment
Labels
A-benchmarking A-sql-optimizer SQL logical planning and optimizations. C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) E-quick-win Likely to be a quick win for someone experienced. T-sql-queries SQL Queries Team
Projects

Comments

@rytaft
Copy link
Collaborator

rytaft commented May 3, 2021

We currently inject pre-calculated statistics for workload fixtures import tpcc, but we do not inject them for workload init tpcc --data-loader IMPORT. Injecting stats helps avoid suboptimal query plans immediately after IMPORT and before the first automatic stats run. Ideally these two approaches should be identical, so we should inject stats in workload init tpcc --data-loader IMPORT too.

Jira issue: CRDB-7140

@rytaft rytaft added C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) A-sql-optimizer SQL logical planning and optimizations. A-benchmarking T-sql-queries SQL Queries Team labels May 3, 2021
@rytaft rytaft added this to Triage in SQL Queries via automation May 3, 2021
@rytaft rytaft added the E-quick-win Likely to be a quick win for someone experienced. label May 5, 2021
@rytaft rytaft moved this from Triage to Backlog in SQL Queries May 5, 2021
@mgartner mgartner moved this from Backlog to New Backlog in SQL Queries Feb 16, 2023
@github-actions
Copy link

We have marked this issue as stale because it has been inactive for
18 months. If this issue is still relevant, removing the stale label
or adding a comment will keep it active. Otherwise, we'll close it in
10 days to keep the issue queue tidy. Thank you for your contribution
to CockroachDB!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-benchmarking A-sql-optimizer SQL logical planning and optimizations. C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) E-quick-win Likely to be a quick win for someone experienced. T-sql-queries SQL Queries Team
Projects
Status: Backlog
SQL Queries
New Backlog
Development

No branches or pull requests

1 participant