refactor: Parallel PG -> Qdrant migration for improved throughput #198
+367
−30
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds support for migrating from PG to Qdrant with parallel batches.
Plus, #199 was merged into this.
How?
Methodology same as #168.
Samples random sorted keys, creates non-overlapping ranges, then workers migrate the ranges independently. Each range tracks its own offset for resumability.
By default
--migration.num-workersis set to the number of CPU cores.If
--migration.num-workersis set to 1, the current sequential migration is used.Results
BEFORE - Migrating 500k points with a batch size of 250.
THIS PR - Migrating 500k points with a batch size of 250 and 8 workers.
About 17x faster.