[Touch-packages] [Bug 1958148] Re: mkinitramfs is too slow

2022-10-31 Thread iMac
Worth noting this had the unintended consequence of temporarily breaking
some modern certified systems, like my XPS 13 9380 when jumping from
22.04 to 22.10, in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1958148

Title:
  mkinitramfs is too slow

Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  On the Nezha board creating an initrd takes more than 1 hour. The
  compression level -19 for zstd is unwisely chosen.

  Here are durations and compression results for an SiFive Unmatched
  board with four cores using zstd:

  -T0 -1 => 13.92s, 136298155 bytes
  -T0 -2 => 15.73s, 131717830 bytes
  -T0 -3 => 26.11s, 127434653 bytes
  -T0 -4 => 29.31s, 126924540 bytes
  -T0 -5 => 36.44s, 125296557 bytes
  -T0 -6 => 39.36s, 124781669 bytes
  -T0 -7 => 46.56s, 116200665 bytes
  -T0 -8 => 51.95s, 113172941 bytes
  -T0 -9 => 55.89s, 112835937 bytes
  -T0 -10 => 61.32s, 108326876 bytes
  -T0 -11 => 64.32s, 108115060 bytes
  -T0 -12 => 76.37s, 108016478 bytes
  -T0 -13 => 148.99s, 109121308 bytes
  -T0 -14 => 156.58s, 108908574 bytes
  -T0 -15 => 228.64s, 109213554 bytes
  -T0 -16 => 380.26s, 107260643 bytes
  -T0 -17 => 453.36s, 103679714 bytes
  -T0 -18 => 714.79s, 100402249 bytes
  -T0 -19 => 1046.58s, 100188713 bytes

  Compression level between -2 to -10 offer a good compromise between
  CPU time and compression results.

  Ideally there would be a parameter that we could pass to mkinitfs. But
  for as fast solution we should simply replace -19 by -9 in
  mkinitramfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1958148] Re: mkinitramfs is too slow

2022-03-16 Thread Launchpad Bug Tracker
This bug was fixed in the package initramfs-tools - 0.140ubuntu13

---
initramfs-tools (0.140ubuntu13) jammy; urgency=medium

  * Lower the compression levels for zstd and lz4 (LP: #1958148)
Following the discussion on the mailing list, we have reached
a conclusion to lower the default compression levels:
- For lz4, the compression level is lowered to 2 from 9
- For zstd, the compression level is lowered to 1 from 19

 -- Julian Andres Klode   Tue, 15 Mar 2022 16:00:55
+0100

** Changed in: initramfs-tools (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1958148

Title:
  mkinitramfs is too slow

Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  On the Nezha board creating an initrd takes more than 1 hour. The
  compression level -19 for zstd is unwisely chosen.

  Here are durations and compression results for an SiFive Unmatched
  board with four cores using zstd:

  -T0 -1 => 13.92s, 136298155 bytes
  -T0 -2 => 15.73s, 131717830 bytes
  -T0 -3 => 26.11s, 127434653 bytes
  -T0 -4 => 29.31s, 126924540 bytes
  -T0 -5 => 36.44s, 125296557 bytes
  -T0 -6 => 39.36s, 124781669 bytes
  -T0 -7 => 46.56s, 116200665 bytes
  -T0 -8 => 51.95s, 113172941 bytes
  -T0 -9 => 55.89s, 112835937 bytes
  -T0 -10 => 61.32s, 108326876 bytes
  -T0 -11 => 64.32s, 108115060 bytes
  -T0 -12 => 76.37s, 108016478 bytes
  -T0 -13 => 148.99s, 109121308 bytes
  -T0 -14 => 156.58s, 108908574 bytes
  -T0 -15 => 228.64s, 109213554 bytes
  -T0 -16 => 380.26s, 107260643 bytes
  -T0 -17 => 453.36s, 103679714 bytes
  -T0 -18 => 714.79s, 100402249 bytes
  -T0 -19 => 1046.58s, 100188713 bytes

  Compression level between -2 to -10 offer a good compromise between
  CPU time and compression results.

  Ideally there would be a parameter that we could pass to mkinitfs. But
  for as fast solution we should simply replace -19 by -9 in
  mkinitramfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1958148] Re: mkinitramfs is too slow

2022-03-15 Thread Brian Murray
As an Ubuntu Release team member I approve of this change.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1958148

Title:
  mkinitramfs is too slow

Status in initramfs-tools package in Ubuntu:
  Fix Committed

Bug description:
  On the Nezha board creating an initrd takes more than 1 hour. The
  compression level -19 for zstd is unwisely chosen.

  Here are durations and compression results for an SiFive Unmatched
  board with four cores using zstd:

  -T0 -1 => 13.92s, 136298155 bytes
  -T0 -2 => 15.73s, 131717830 bytes
  -T0 -3 => 26.11s, 127434653 bytes
  -T0 -4 => 29.31s, 126924540 bytes
  -T0 -5 => 36.44s, 125296557 bytes
  -T0 -6 => 39.36s, 124781669 bytes
  -T0 -7 => 46.56s, 116200665 bytes
  -T0 -8 => 51.95s, 113172941 bytes
  -T0 -9 => 55.89s, 112835937 bytes
  -T0 -10 => 61.32s, 108326876 bytes
  -T0 -11 => 64.32s, 108115060 bytes
  -T0 -12 => 76.37s, 108016478 bytes
  -T0 -13 => 148.99s, 109121308 bytes
  -T0 -14 => 156.58s, 108908574 bytes
  -T0 -15 => 228.64s, 109213554 bytes
  -T0 -16 => 380.26s, 107260643 bytes
  -T0 -17 => 453.36s, 103679714 bytes
  -T0 -18 => 714.79s, 100402249 bytes
  -T0 -19 => 1046.58s, 100188713 bytes

  Compression level between -2 to -10 offer a good compromise between
  CPU time and compression results.

  Ideally there would be a parameter that we could pass to mkinitfs. But
  for as fast solution we should simply replace -19 by -9 in
  mkinitramfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1958148] Re: mkinitramfs is too slow

2022-03-15 Thread Julian Andres Klode
I have uploaded the agreed changes (attached) to jammy.

** Patch added: "initramfs-tools_0.140ubuntu13.diff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+attachment/5569316/+files/initramfs-tools_0.140ubuntu13.diff

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1958148

Title:
  mkinitramfs is too slow

Status in initramfs-tools package in Ubuntu:
  Fix Committed

Bug description:
  On the Nezha board creating an initrd takes more than 1 hour. The
  compression level -19 for zstd is unwisely chosen.

  Here are durations and compression results for an SiFive Unmatched
  board with four cores using zstd:

  -T0 -1 => 13.92s, 136298155 bytes
  -T0 -2 => 15.73s, 131717830 bytes
  -T0 -3 => 26.11s, 127434653 bytes
  -T0 -4 => 29.31s, 126924540 bytes
  -T0 -5 => 36.44s, 125296557 bytes
  -T0 -6 => 39.36s, 124781669 bytes
  -T0 -7 => 46.56s, 116200665 bytes
  -T0 -8 => 51.95s, 113172941 bytes
  -T0 -9 => 55.89s, 112835937 bytes
  -T0 -10 => 61.32s, 108326876 bytes
  -T0 -11 => 64.32s, 108115060 bytes
  -T0 -12 => 76.37s, 108016478 bytes
  -T0 -13 => 148.99s, 109121308 bytes
  -T0 -14 => 156.58s, 108908574 bytes
  -T0 -15 => 228.64s, 109213554 bytes
  -T0 -16 => 380.26s, 107260643 bytes
  -T0 -17 => 453.36s, 103679714 bytes
  -T0 -18 => 714.79s, 100402249 bytes
  -T0 -19 => 1046.58s, 100188713 bytes

  Compression level between -2 to -10 offer a good compromise between
  CPU time and compression results.

  Ideally there would be a parameter that we could pass to mkinitfs. But
  for as fast solution we should simply replace -19 by -9 in
  mkinitramfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1958148] Re: mkinitramfs is too slow

2022-03-14 Thread Michael Hudson-Doyle
** Changed in: initramfs-tools (Ubuntu)
   Importance: Medium => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1958148

Title:
  mkinitramfs is too slow

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  On the Nezha board creating an initrd takes more than 1 hour. The
  compression level -19 for zstd is unwisely chosen.

  Here are durations and compression results for an SiFive Unmatched
  board with four cores using zstd:

  -T0 -1 => 13.92s, 136298155 bytes
  -T0 -2 => 15.73s, 131717830 bytes
  -T0 -3 => 26.11s, 127434653 bytes
  -T0 -4 => 29.31s, 126924540 bytes
  -T0 -5 => 36.44s, 125296557 bytes
  -T0 -6 => 39.36s, 124781669 bytes
  -T0 -7 => 46.56s, 116200665 bytes
  -T0 -8 => 51.95s, 113172941 bytes
  -T0 -9 => 55.89s, 112835937 bytes
  -T0 -10 => 61.32s, 108326876 bytes
  -T0 -11 => 64.32s, 108115060 bytes
  -T0 -12 => 76.37s, 108016478 bytes
  -T0 -13 => 148.99s, 109121308 bytes
  -T0 -14 => 156.58s, 108908574 bytes
  -T0 -15 => 228.64s, 109213554 bytes
  -T0 -16 => 380.26s, 107260643 bytes
  -T0 -17 => 453.36s, 103679714 bytes
  -T0 -18 => 714.79s, 100402249 bytes
  -T0 -19 => 1046.58s, 100188713 bytes

  Compression level between -2 to -10 offer a good compromise between
  CPU time and compression results.

  Ideally there would be a parameter that we could pass to mkinitfs. But
  for as fast solution we should simply replace -19 by -9 in
  mkinitramfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1958148] Re: mkinitramfs is too slow

2022-03-07 Thread Sebastien Bacher
@re discussion, there has been some posts about the topic at least on
https://lists.ubuntu.com/archives/ubuntu-devel/2021-December/041726.html

it feels like we would need a feature freeze exception at this point for
a such change, or at least an ack from ubuntu release

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1958148

Title:
  mkinitramfs is too slow

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  On the Nezha board creating an initrd takes more than 1 hour. The
  compression level -19 for zstd is unwisely chosen.

  Here are durations and compression results for an SiFive Unmatched
  board with four cores using zstd:

  -T0 -1 => 13.92s, 136298155 bytes
  -T0 -2 => 15.73s, 131717830 bytes
  -T0 -3 => 26.11s, 127434653 bytes
  -T0 -4 => 29.31s, 126924540 bytes
  -T0 -5 => 36.44s, 125296557 bytes
  -T0 -6 => 39.36s, 124781669 bytes
  -T0 -7 => 46.56s, 116200665 bytes
  -T0 -8 => 51.95s, 113172941 bytes
  -T0 -9 => 55.89s, 112835937 bytes
  -T0 -10 => 61.32s, 108326876 bytes
  -T0 -11 => 64.32s, 108115060 bytes
  -T0 -12 => 76.37s, 108016478 bytes
  -T0 -13 => 148.99s, 109121308 bytes
  -T0 -14 => 156.58s, 108908574 bytes
  -T0 -15 => 228.64s, 109213554 bytes
  -T0 -16 => 380.26s, 107260643 bytes
  -T0 -17 => 453.36s, 103679714 bytes
  -T0 -18 => 714.79s, 100402249 bytes
  -T0 -19 => 1046.58s, 100188713 bytes

  Compression level between -2 to -10 offer a good compromise between
  CPU time and compression results.

  Ideally there would be a parameter that we could pass to mkinitfs. But
  for as fast solution we should simply replace -19 by -9 in
  mkinitramfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1958148] Re: mkinitramfs is too slow

2022-03-07 Thread Heinrich Schuchardt
** Changed in: initramfs-tools (Ubuntu)
   Status: In Progress => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1958148

Title:
  mkinitramfs is too slow

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  On the Nezha board creating an initrd takes more than 1 hour. The
  compression level -19 for zstd is unwisely chosen.

  Here are durations and compression results for an SiFive Unmatched
  board with four cores using zstd:

  -T0 -1 => 13.92s, 136298155 bytes
  -T0 -2 => 15.73s, 131717830 bytes
  -T0 -3 => 26.11s, 127434653 bytes
  -T0 -4 => 29.31s, 126924540 bytes
  -T0 -5 => 36.44s, 125296557 bytes
  -T0 -6 => 39.36s, 124781669 bytes
  -T0 -7 => 46.56s, 116200665 bytes
  -T0 -8 => 51.95s, 113172941 bytes
  -T0 -9 => 55.89s, 112835937 bytes
  -T0 -10 => 61.32s, 108326876 bytes
  -T0 -11 => 64.32s, 108115060 bytes
  -T0 -12 => 76.37s, 108016478 bytes
  -T0 -13 => 148.99s, 109121308 bytes
  -T0 -14 => 156.58s, 108908574 bytes
  -T0 -15 => 228.64s, 109213554 bytes
  -T0 -16 => 380.26s, 107260643 bytes
  -T0 -17 => 453.36s, 103679714 bytes
  -T0 -18 => 714.79s, 100402249 bytes
  -T0 -19 => 1046.58s, 100188713 bytes

  Compression level between -2 to -10 offer a good compromise between
  CPU time and compression results.

  Ideally there would be a parameter that we could pass to mkinitfs. But
  for as fast solution we should simply replace -19 by -9 in
  mkinitramfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1958148] Re: mkinitramfs is too slow

2022-03-01 Thread Heinrich Schuchardt
** Patch added: "initramfs-tools-0.140ubuntu12..0.140ubuntu13.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+attachment/5564513/+files/initramfs-tools-0.140ubuntu12..0.140ubuntu13.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1958148

Title:
  mkinitramfs is too slow

Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  On the Nezha board creating an initrd takes more than 1 hour. The
  compression level -19 for zstd is unwisely chosen.

  Here are durations and compression results for an SiFive Unmatched
  board with four cores using zstd:

  -T0 -1 => 13.92s, 136298155 bytes
  -T0 -2 => 15.73s, 131717830 bytes
  -T0 -3 => 26.11s, 127434653 bytes
  -T0 -4 => 29.31s, 126924540 bytes
  -T0 -5 => 36.44s, 125296557 bytes
  -T0 -6 => 39.36s, 124781669 bytes
  -T0 -7 => 46.56s, 116200665 bytes
  -T0 -8 => 51.95s, 113172941 bytes
  -T0 -9 => 55.89s, 112835937 bytes
  -T0 -10 => 61.32s, 108326876 bytes
  -T0 -11 => 64.32s, 108115060 bytes
  -T0 -12 => 76.37s, 108016478 bytes
  -T0 -13 => 148.99s, 109121308 bytes
  -T0 -14 => 156.58s, 108908574 bytes
  -T0 -15 => 228.64s, 109213554 bytes
  -T0 -16 => 380.26s, 107260643 bytes
  -T0 -17 => 453.36s, 103679714 bytes
  -T0 -18 => 714.79s, 100402249 bytes
  -T0 -19 => 1046.58s, 100188713 bytes

  Compression level between -2 to -10 offer a good compromise between
  CPU time and compression results.

  Ideally there would be a parameter that we could pass to mkinitfs. But
  for as fast solution we should simply replace -19 by -9 in
  mkinitramfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1958148] Re: mkinitramfs is too slow

2022-02-28 Thread Trent Lloyd
Where is the discussion happening?

I ran the same benchmarks for my i7-6770HQ 4-core system. This really
needs revising.

While disk space using in /boot is a concern, in this example at least
-10 would use only 8MB (10%) more space and cut the time taken from 2m1s
to 13s.

zstd.0 84M 0m2.150s
zstd.1 96M 0m1.236s
zstd.2 90M 0m1.350s
zstd.3 84M 0m2.235s
zstd.4 84M 0m3.355s
zstd.5 81M 0m5.679s
zstd.6 81M 0m7.416s
zstd.7 78M 0m8.857s
zstd.8 77M 0m10.134s
zstd.9 77M 0m11.238s
zstd.10 72M 0m13.232s
zstd.11 72M 0m14.897s
zstd.12 72M 0m19.343s
zstd.13 72M 0m26.327s
zstd.14 72M 0m30.948s
zstd.15 72M 0m40.913s
zstd.16 70M 0m59.517s
zstd.17 66M 1m15.854s
zstd.18 64M 1m36.227s
zstd.19 64M 2m1.417s

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1958148

Title:
  mkinitramfs is too slow

Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  On the Nezha board creating an initrd takes more than 1 hour. The
  compression level -19 for zstd is unwisely chosen.

  Here are durations and compression results for an SiFive Unmatched
  board with four cores using zstd:

  -T0 -1 => 13.92s, 136298155 bytes
  -T0 -2 => 15.73s, 131717830 bytes
  -T0 -3 => 26.11s, 127434653 bytes
  -T0 -4 => 29.31s, 126924540 bytes
  -T0 -5 => 36.44s, 125296557 bytes
  -T0 -6 => 39.36s, 124781669 bytes
  -T0 -7 => 46.56s, 116200665 bytes
  -T0 -8 => 51.95s, 113172941 bytes
  -T0 -9 => 55.89s, 112835937 bytes
  -T0 -10 => 61.32s, 108326876 bytes
  -T0 -11 => 64.32s, 108115060 bytes
  -T0 -12 => 76.37s, 108016478 bytes
  -T0 -13 => 148.99s, 109121308 bytes
  -T0 -14 => 156.58s, 108908574 bytes
  -T0 -15 => 228.64s, 109213554 bytes
  -T0 -16 => 380.26s, 107260643 bytes
  -T0 -17 => 453.36s, 103679714 bytes
  -T0 -18 => 714.79s, 100402249 bytes
  -T0 -19 => 1046.58s, 100188713 bytes

  Compression level between -2 to -10 offer a good compromise between
  CPU time and compression results.

  Ideally there would be a parameter that we could pass to mkinitfs. But
  for as fast solution we should simply replace -19 by -9 in
  mkinitramfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1958148] Re: mkinitramfs is too slow

2022-02-21 Thread Julian Andres Klode
Unsubscribed ubuntu-sponsors as the default compression level is still
an ongoing discussion.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1958148

Title:
  mkinitramfs is too slow

Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  On the Nezha board creating an initrd takes more than 1 hour. The
  compression level -19 for zstd is unwisely chosen.

  Here are durations and compression results for an SiFive Unmatched
  board with four cores using zstd:

  -T0 -1 => 13.92s, 136298155 bytes
  -T0 -2 => 15.73s, 131717830 bytes
  -T0 -3 => 26.11s, 127434653 bytes
  -T0 -4 => 29.31s, 126924540 bytes
  -T0 -5 => 36.44s, 125296557 bytes
  -T0 -6 => 39.36s, 124781669 bytes
  -T0 -7 => 46.56s, 116200665 bytes
  -T0 -8 => 51.95s, 113172941 bytes
  -T0 -9 => 55.89s, 112835937 bytes
  -T0 -10 => 61.32s, 108326876 bytes
  -T0 -11 => 64.32s, 108115060 bytes
  -T0 -12 => 76.37s, 108016478 bytes
  -T0 -13 => 148.99s, 109121308 bytes
  -T0 -14 => 156.58s, 108908574 bytes
  -T0 -15 => 228.64s, 109213554 bytes
  -T0 -16 => 380.26s, 107260643 bytes
  -T0 -17 => 453.36s, 103679714 bytes
  -T0 -18 => 714.79s, 100402249 bytes
  -T0 -19 => 1046.58s, 100188713 bytes

  Compression level between -2 to -10 offer a good compromise between
  CPU time and compression results.

  Ideally there would be a parameter that we could pass to mkinitfs. But
  for as fast solution we should simply replace -19 by -9 in
  mkinitramfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1958148] Re: mkinitramfs is too slow

2022-01-24 Thread Mathew Hodson
** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1958148

Title:
  mkinitramfs is too slow

Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  On the Nezha board creating an initrd takes more than 1 hour. The
  compression level -19 for zstd is unwisely chosen.

  Here are durations and compression results for an SiFive Unmatched
  board with four cores using zstd:

  -T0 -1 => 13.92s, 136298155 bytes
  -T0 -2 => 15.73s, 131717830 bytes
  -T0 -3 => 26.11s, 127434653 bytes
  -T0 -4 => 29.31s, 126924540 bytes
  -T0 -5 => 36.44s, 125296557 bytes
  -T0 -6 => 39.36s, 124781669 bytes
  -T0 -7 => 46.56s, 116200665 bytes
  -T0 -8 => 51.95s, 113172941 bytes
  -T0 -9 => 55.89s, 112835937 bytes
  -T0 -10 => 61.32s, 108326876 bytes
  -T0 -11 => 64.32s, 108115060 bytes
  -T0 -12 => 76.37s, 108016478 bytes
  -T0 -13 => 148.99s, 109121308 bytes
  -T0 -14 => 156.58s, 108908574 bytes
  -T0 -15 => 228.64s, 109213554 bytes
  -T0 -16 => 380.26s, 107260643 bytes
  -T0 -17 => 453.36s, 103679714 bytes
  -T0 -18 => 714.79s, 100402249 bytes
  -T0 -19 => 1046.58s, 100188713 bytes

  Compression level between -2 to -10 offer a good compromise between
  CPU time and compression results.

  Ideally there would be a parameter that we could pass to mkinitfs. But
  for as fast solution we should simply replace -19 by -9 in
  mkinitramfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1958148] Re: mkinitramfs is too slow

2022-01-18 Thread Heinrich Schuchardt
** Tags added: fr-1977

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1958148

Title:
  mkinitramfs is too slow

Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  On the Nezha board creating an initrd takes more than 1 hour. The
  compression level -19 for zstd is unwisely chosen.

  Here are durations and compression results for an SiFive Unmatched
  board with four cores using zstd:

  -T0 -1 => 13.92s, 136298155 bytes
  -T0 -2 => 15.73s, 131717830 bytes
  -T0 -3 => 26.11s, 127434653 bytes
  -T0 -4 => 29.31s, 126924540 bytes
  -T0 -5 => 36.44s, 125296557 bytes
  -T0 -6 => 39.36s, 124781669 bytes
  -T0 -7 => 46.56s, 116200665 bytes
  -T0 -8 => 51.95s, 113172941 bytes
  -T0 -9 => 55.89s, 112835937 bytes
  -T0 -10 => 61.32s, 108326876 bytes
  -T0 -11 => 64.32s, 108115060 bytes
  -T0 -12 => 76.37s, 108016478 bytes
  -T0 -13 => 148.99s, 109121308 bytes
  -T0 -14 => 156.58s, 108908574 bytes
  -T0 -15 => 228.64s, 109213554 bytes
  -T0 -16 => 380.26s, 107260643 bytes
  -T0 -17 => 453.36s, 103679714 bytes
  -T0 -18 => 714.79s, 100402249 bytes
  -T0 -19 => 1046.58s, 100188713 bytes

  Compression level between -2 to -10 offer a good compromise between
  CPU time and compression results.

  Ideally there would be a parameter that we could pass to mkinitfs. But
  for as fast solution we should simply replace -19 by -9 in
  mkinitramfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1958148] Re: mkinitramfs is too slow

2022-01-18 Thread Heinrich Schuchardt
initramfs-tools - 0.140ubuntu11 is available in ppa:xypron/gnu-efi and
needs a sponsor.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1958148

Title:
  mkinitramfs is too slow

Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  On the Nezha board creating an initrd takes more than 1 hour. The
  compression level -19 for zstd is unwisely chosen.

  Here are durations and compression results for an SiFive Unmatched
  board with four cores using zstd:

  -T0 -1 => 13.92s, 136298155 bytes
  -T0 -2 => 15.73s, 131717830 bytes
  -T0 -3 => 26.11s, 127434653 bytes
  -T0 -4 => 29.31s, 126924540 bytes
  -T0 -5 => 36.44s, 125296557 bytes
  -T0 -6 => 39.36s, 124781669 bytes
  -T0 -7 => 46.56s, 116200665 bytes
  -T0 -8 => 51.95s, 113172941 bytes
  -T0 -9 => 55.89s, 112835937 bytes
  -T0 -10 => 61.32s, 108326876 bytes
  -T0 -11 => 64.32s, 108115060 bytes
  -T0 -12 => 76.37s, 108016478 bytes
  -T0 -13 => 148.99s, 109121308 bytes
  -T0 -14 => 156.58s, 108908574 bytes
  -T0 -15 => 228.64s, 109213554 bytes
  -T0 -16 => 380.26s, 107260643 bytes
  -T0 -17 => 453.36s, 103679714 bytes
  -T0 -18 => 714.79s, 100402249 bytes
  -T0 -19 => 1046.58s, 100188713 bytes

  Compression level between -2 to -10 offer a good compromise between
  CPU time and compression results.

  Ideally there would be a parameter that we could pass to mkinitfs. But
  for as fast solution we should simply replace -19 by -9 in
  mkinitramfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp