Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

This tracks improvements to Pulp import and export performance which have been / are being made in response to customer discussions.

Version-Release number of selected component (if applicable):
6.11+

Steps to Reproduce:
1.  Create a sufficiently large installation e.g. by syncing these repos https://bugzilla.redhat.com/show_bug.cgi?id=2238906#c2
2.  Perform a content export
3.  Perform an import of the same export archive

Newer versions should see a significant performance improvement over current releases

These 3 BZs ought to be tested together as they involve essentially the same setup process

https://bugzilla.redhat.com/show_bug.cgi?id=2238906
https://bugzilla.redhat.com/show_bug.cgi?id=2228592
https://bugzilla.redhat.com/show_bug.cgi?id=2244521 (this one)

Looks like these fixes are already present in both of the releases (6.13, 6.14) for which it's still marked, and has been for a while.

It probably slipped through the system because there were multiple BZs covering the same essential issues, as mentioned in comment #1.  Since those other issues are covering the same ground, and they've already been verified, and given it's already shipped, probably easiest to just close this out.