Bug 2244521

Summary:	Imports and Exports are not sufficiently optimized
Product:	Red Hat Satellite	Reporter:	Daniel Alley <dalley>
Component:	Pulp	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.11.5	CC:	dkliban, ggainey, rchan, rlavi
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	pulpcore-3.16.23, pulpcore-3.18.31, pulpcore-3.21.21, pulpcore-3.22.17, pulpcore-3.28.18	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-05-30 05:01:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Daniel Alley 2023-10-16 18:20:26 UTC

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

Comment 1 Daniel Alley 2023-10-16 18:25:11 UTC

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)

Comment 3 Daniel Alley 2024-05-30 05:01:09 UTC

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.