Bug 2239183

Summary: Gzip level 1 compression is still too high for many users of import/export
Product: Red Hat Satellite Reporter: Robin Chan <rchan>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: UnspecifiedCC: ahumbe, dalley, dkliban, ggainey, rchan, rlavi
Target Milestone: UnspecifiedKeywords: 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-09-18 18:59:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Robin Chan 2023-09-15 19:05:08 UTC
Even the lowest level of gzip compression, level 1, consumes an inordinate and disproportionately high amount of compute time compared to the benefit received from the compression (which is in most cases tiny, since often the data is compressed to begin with)

For example with no compression at all, an export of CentOS Stream 9 BaseOS + RHEL 9 BaseOS required 11.8gb of disk.

With Level 1 compression, it required 11.4gb.  With Level 9 compression, it required 11.3gb.

For this result, on my system, 63% of the export time was spent on compressing the exports.  Going from level 9 to level 1 to level 0 brought the runtime from 10.5min, to 8.5min, to 4min respectively.

Users of import/export are often dealing with data on the scale of hundreds of gigabytes or multiple terabytes, and disk space seems to be less an issue than the amount of time these exports take.  It's best that we default to no compression at all, and look at making it configurable later.

Luckily "gzip level 0" does exist, and packs everything into a gzip archive without performing compression.  So we can drop this change in without breaking compatibility with anything.

Comment 1 Robin Chan 2023-09-15 20:05:25 UTC
The Pulp upstream bug status is at open. Updating the external tracker on this bug.

Comment 2 Robin Chan 2023-09-18 15:05:37 UTC
The Pulp upstream bug status is at closed. Updating the external tracker on this bug.

Comment 3 Robin Chan 2023-09-18 15:05:39 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.

Comment 4 Daniel Alley 2023-09-18 18:59:14 UTC

*** This bug has been marked as a duplicate of bug 2188504 ***