Task #3824
closed
Migration Plugin - Story #3821: As a user, I can migrate from Pulp 2 to Pulp 3
Analyze repository version creation performance for pulp_rpm
0%
Description
After the user has migrated content from Pulp 2 to Pulp 3, it will be necesary to migrate the repositories and the association between repos and content. There are 2 options for migrating the association:
- create a repository version by performing a sync from Pulp 2 repository
- create a repository version by querying Pulp 2, find units in Pulp 3, create a repository version by specifying the pulp 3 units.
This task is to analyze the performance of the two methods of creating repository versions and provide guidance on how this part of the migration should be handled.
Updated by dkliban@redhat.com almost 6 years ago
- Tracker changed from Issue to Task
- % Done set to 0
- Parent issue set to #3821
Updated by daviddavis about 5 years ago
- Subject changed from Analize repository version creation performance for pulp_rpm to Analyze repository version creation performance for pulp_rpm
Updated by ttereshc about 4 years ago
- Sprint/Milestone set to Pulp 3.x RPM (Katello 3.16)
Updated by dalley about 4 years ago
- Status changed from NEW to CLOSED - COMPLETE
Some performance discussion here with graphs: https://github.com/pulp/pulp-2to3-migration/pull/120
TL;DR current performance is:
~80 seconds for initial migration ~50 seconds for re-migrations
A fresh sync in Pulp 3 is ~50 seconds without content downloading. But the migration does sync+publish, so it's a little faster (not much)
Updated by ggainey almost 4 years ago
- Tags Katello added
- Tags deleted (
Katello-P1)
.