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.
Bug 2239183 - Gzip level 1 compression is still too high for many users of import/export
Summary: Gzip level 1 compression is still too high for many users of import/export
Keywords:
Status: CLOSED DUPLICATE of bug 2188504
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-09-15 19:05 UTC by Robin Chan
Modified: 2023-09-18 18:59 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-18 18:59:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github /pulp pulpcore issues 4434 0 None closed Gzip level 1 compression is still too high for many users of import/export 2023-09-18 15:05:36 UTC
Red Hat Issue Tracker SAT-20144 0 None None None 2023-09-15 19:05:47 UTC

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 ***


Note You need to log in before you can comment on or make changes to this bug.