Feature #18348
Foreman debug is very slow for big tarballs
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assigned To: |  Lukas Zapletal | ||
| Category: | foreman-debug | ||
| Target version: | Team Daniel - Iteration 9 | ||
| Difficulty: | Bugzilla link: | ||
| Found in release: | Pull request: | https://github.com/theforeman/foreman/pull/4248 | |
| Story points | - | ||
| Velocity based estimate | - | ||
| Release | 1.15.0 | Release relationship | Auto |
Description
Due to compression default settings in debug, big tarballs can be very slow to create due compression. After taking a look at
https://catchchallenger.first-world.info/wiki/Quick_Benchmark:_Gzip_vs_Bzip2_vs_LZMA_vs_XZ_vs_LZ4_vs_LZO I want to change this a bit:
Today, foreman-debug tries to find compressors in this order (and options):
- xz -9
- bzip2 -9
- gzip -9
This usually ends up with xz or bzip2 but both are remarebly slower with -9 option, so what I suggest now:
- xz -1
- bzip2 -1
- gzip -5
Both xz and bzip2 are the same speed as gzip -5 and giving similar (slightly better) ratio.
Overall compression should be about 4 times faster after this patch.
Associated revisions
Fixes #18348 - foreman-debug compress faster
History
#1
Updated by The Foreman Bot about 1 year ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/4248 added
#2
Updated by Lukas Zapletal about 1 year ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset e670682168870b3f419c631834e042a53be17242.
#3
Updated by Dominic Cleal about 1 year ago
- Release set to 1.15.0
#4
Updated by Daniel Lobato Garcia about 1 year ago
- Target version set to Team Daniel - Iteration 9