Migration Plugin - Story #3821: As a user, I can migrate from Pulp 2 to Pulp 3
Analyze repository version creation performance for pulp_rpm
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.
#6 Updated by dalley over 1 year 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)
Please register to edit this issue