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.

Sign up for GitHub

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

Jump to bottom

importccl: mysql and postgres import are slow #32173

Closed
maddyblue opened this issue Nov 7, 2018 · 2 comments
Closed

importccl: mysql and postgres import are slow #32173

maddyblue opened this issue Nov 7, 2018 · 2 comments
Labels
A-disaster-recovery C-performance Perf of queries or internals. Solution not expected to change functional behavior. T-disaster-recovery
Projects
Disaster Recovery Backlog

Comments

@maddyblue
Copy link
Contributor

maddyblue commented Nov 7, 2018 •
edited by cockroach-jira-scripts

The first stage of mysql and postgres import are slow because they are limited to a single core on a single node. Work needs to be done to enable multicore processing.

Epic CRDB-2340

Jira issue: CRDB-4759
@maddyblue maddyblue added C-performance Perf of queries or internals. Solution not expected to change functional behavior. A-disaster-recovery labels Nov 7, 2018
@maddyblue maddyblue added this to Triage in Bulk IO via automation Nov 7, 2018
@LordFPL
Copy link

LordFPL commented Nov 8, 2018

+1

@dt dt added this to Triage in Disaster Recovery Backlog via automation Jul 8, 2019
@dt dt removed this from Triage in Bulk IO Jul 8, 2019
@dt dt moved this from Triage to Polish/New Features in Disaster Recovery Backlog Jul 11, 2019
@dt dt moved this from Features and Polish to sort into Backlogs to Backlog: IMPORT in Disaster Recovery Backlog Jul 16, 2019
@dikshant
Copy link

dikshant commented Feb 2, 2023

With IMPORT MYSQLDUMP and IMPORT PGDUMP being deprecated: #93660 and Schema Conversion Tool being better for schema migrations this is no longer needed and can now be closed.

@dikshant dikshant closed this as completed Feb 2, 2023
Disaster Recovery Backlog automation moved this from Import/Export to Done Feb 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-disaster-recovery C-performance Perf of queries or internals. Solution not expected to change functional behavior. T-disaster-recovery
Projects
Disaster Recovery Backlog
Done
Milestone
No milestone
Development

No branches or pull requests
4 participants
@maddyblue @kenliu @LordFPL @dikshant