-
Notifications
You must be signed in to change notification settings - Fork 4.1k
import: add an import test into roachperf so we can monitor it over time #146490
Copy link
Copy link
Open
Labels
A-importIssues related to IMPORT syntaxIssues related to IMPORT syntaxC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)O-postmortemOriginated from a Postmortem action item.Originated from a Postmortem action item.P-3Issues/test failures with no fix SLAIssues/test failures with no fix SLAT-sql-foundationsSQL Foundations Team (formerly SQL Schema + SQL Sessions)SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Description
Metadata
Metadata
Assignees
Labels
A-importIssues related to IMPORT syntaxIssues related to IMPORT syntaxC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)O-postmortemOriginated from a Postmortem action item.Originated from a Postmortem action item.P-3Issues/test failures with no fix SLAIssues/test failures with no fix SLAT-sql-foundationsSQL Foundations Team (formerly SQL Schema + SQL Sessions)SQL Foundations Team (formerly SQL Schema + SQL Sessions)
We monitor the performance of some operations over time using roachperf. For example, we monitor RESTORE. We should add a similar test for IMPORT to ensure that we don't regress performance.
Jira issue: CRDB-50546
Epic CRDB-62881