Feature #18348

Foreman debug is very slow for big tarballs

Added by Lukas Zapletal 5 months ago. Updated 4 months ago.

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-
Release1.15.0Release relationshipAuto

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

Revision e6706821
Added by Lukas Zapletal 5 months ago

Fixes #18348 - foreman-debug compress faster

History

#1 Updated by The Foreman Bot 5 months ago

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

#2 Updated by Lukas Zapletal 5 months ago

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

#3 Updated by Dominic Cleal 5 months ago

  • Release set to 1.15.0

#4 Updated by Daniel Lobato Garcia 4 months ago

  • Target version set to Team Daniel - Iteration 9

Also available in: Atom PDF