Project

Profile

Help

Actions
Send by e-mail Copy link

Issue #7183

closed

Content pre-migration and migration is too slow

Added by dalley over 3 years ago. Updated over 3 years ago.

Status:
CLOSED - NOTABUG
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

On my system, with 8 pulp2 repositories comprised of about 183,000 content units, re-migration takes 15+ minutes which is still not where we would like it to be (a couple of minutes). Content migration and pre-migration is ~87% of the total runtime here.

Initial migration

Re-migration

Files

Download all files
migration_performance_initial.png (2.07 MB) migration_performance_initial.png dalley, 07/29/2020 03:31 PM
migration_performance_remigration.png (1.47 MB) migration_performance_remigration.png dalley, 07/29/2020 03:31 PM
Actions
Copy link
 #1

Updated by dalley over 3 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by dalley over 3 years ago

Pre-migrating the lazy catalog takes up nearly 50% of re-migration time, that would probably be a good place to start.

Actions
Copy link
 #3

Updated by dalley over 3 years ago

  • Description updated (diff)
Actions
Copy link
 #4

Updated by dalley over 3 years ago

  • File deleted (many_repo_re_migration.png)
Actions
Copy link
 #5

Updated by dalley over 3 years ago

  • File deleted (many_repo_initial_migration.png)
Actions
Copy link
 #6

Updated by dalley over 3 years ago

Actions
Copy link
 #7

Updated by dalley over 3 years ago

  • Status changed from NEW to POST
  • Assignee set to dalley
Actions
Copy link
 #8

Updated by dalley over 3 years ago

  • Status changed from POST to CLOSED - NOTABUG
  • Assignee deleted (dalley)

Mostly an artifact of other bugs -- and improvements have been made here also

Actions
Send by e-mail Copy link

Also available in: Atom PDF