Bug 2228592

Summary:	Incremental export using fs-export generates very slow queries and takes huge time to export
Product:	Red Hat Satellite	Reporter:	Joniel Pasqualetto <jpasqual>
Component:	Pulp	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.12.4	CC:	ahumbe, dalley, mkalyat, rlavi
Target Milestone:	Unspecified	Keywords:	Performance, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-10-18 13:04:24 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 Joniel Pasqualetto 2023-08-02 19:14:24 UTC

Description of problem:

Very big library (complete export of 1.5Tb). When trying to generate an incremental export of the library (all repositories), a very long time is spent on some DB queries. 

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


How reproducible:
Unsure. All the time on customer's environment

Steps to Reproduce:
In theory, that's what customer did:

1. Generate complete export of big library
2. After a while, generate incremental exports using fs-export (syncable method)


Actual results:
Export works, but is very slow. Last test from customer took 24h running. Result had 3.5Gb of data (which is not wrong, just time to generate it is considered too long)

Expected results:

Export to finish faster.

Additional info:

Comment 2 Daniel Alley 2023-08-07 18:58:02 UTC

I don't know that this is one issue, but perhaps a combination of https://github.com/pulp/pulpcore/pull/4161 (which is already tracked by BZ https://bugzilla.redhat.com/show_bug.cgi?id=2226950) and https://github.com/pulp/pulpcore/issues/3969 ?

We have that work in progress currently for other stakeholders anyway, so we can check back in shortly when it is finished and see if the situation is improved.

Comment 18 Daniel Alley 2023-10-16 18:24:20 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 (this one)
https://bugzilla.redhat.com/show_bug.cgi?id=2244521