CockroachDB + migrate: figure out source and impact of slowness
See original GitHub issueFrom first hand experience, using prisma migrate dev
with cockroachdb is slow.
- Does it happen on all versions/deployments of cockroachdb? The prisma test docker image has a bunch of custom settings.
- Where does the slowness come from?
- Do we still consider it an acceptable user experience?
- If not, use findings from previous steps to come up with potential improvements.
- As a last resort, figure out ways to provide more frequent feedback on command progress
Issue Analytics
- State:
- Created 2 years ago
- Comments:15 (2 by maintainers)
Top Results From Across the Web
Migrate Your Database to CockroachDB
Step 1. Test and update your schema. To begin a new migration to CockroachDB, extract the data definition language (DDL) of the source...
Read more >Migrate CockroachDB Schemas with Flyway
This tutorial guides you through a series of simple database schema changes using Flyway, an open-source schema migration tool.
Read more >CockroachDB 2.1 — Easier Migrations and a 5x Scalability ...
In CockroachDB 2.1, we've made it easier than ever to migrate from MySQL and Postgres, improved our scalability on transactional workloads ...
Read more >Known Limitations in CockroachDB v22.2
This page describes newly identified limitations in the CockroachDB v22.2.0 release as well as unresolved limitations identified in earlier releases.
Read more >Migrate with AWS Database Migration Service (DMS)
This page has instructions for setting up AWS Database Migration Service (DMS) to migrate data to CockroachDB from an existing, publicly hosted database ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The tool was initially just not created with that use case in mind, so we prioritized running each migration one by one. This feedback will help us to potentially reconsider that 👍
We have a few tracking issues for slowness in schema changes on our side. We have made progress on a few of them for the v22.1 release. The worst case is when adding and dropping things repeatedly, which is common in tests.
I’m definitely curious to see the extra details about when the slowness happens. With that, hopefully we can drill further, and potentially link to relevant issues on our side.