Project

General

Profile

Actions

Feature #18348

closed

Foreman debug is very slow for big tarballs

Added by Lukas Zapletal about 7 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
foreman-debug
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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.

Actions #1

Updated by The Foreman Bot about 7 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/4248 added
Actions #2

Updated by Lukas Zapletal about 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #3

Updated by Dominic Cleal about 7 years ago

  • translation missing: en.field_release set to 209
Actions #4

Updated by Daniel Lobato Garcia about 7 years ago

  • Target version set to 1.11.0
Actions

Also available in: Atom PDF