Re: Revisiting default initramfs compression

2021-12-08 Thread Dimitri John Ledkov
On Wed, 8 Dec 2021, 17:13 Julian Andres Klode, wrote: > Hi all, > > some time ago, the default compressor for initramfs was changed > from lz4 -9 to zstd -19. This caused significant problems: > > - it is very slow > - it uses a lot of memory > > The former is a problem for everyone, the latter

Re: status of ccache and libhiredis in main

2021-12-08 Thread Michael Hudson-Doyle
On Tue, 7 Dec 2021 at 03:19, Lukas Märdian wrote: > > > On Sun, Dec 5, 2021 at 7:38 PM Jeremy Bicha wrote: > >> On Tue, Nov 30, 2021 at 10:22 PM Michael Hudson-Doyle >> wrote: >> > It turns out that ccache has been in main essentially forever, since >> 2004 and there is no formal record of the

Re: Revisiting default initramfs compression

2021-12-08 Thread Dave Jones
Firstly, many thanks for Julian for starting this thread; I've had far too much fun delving back into some SQL+jupyter notebooks today while gathering a bit more info on this... If you just want to go see or play with the data (and possibly expand it with some more samples; I'd love to see

Re: Revisiting default initramfs compression

2021-12-08 Thread Steve Langasek
Thanks for raising this discussion, Julian! On Wed, Dec 08, 2021 at 06:12:43PM +0100, Julian Andres Klode wrote: > ## Adaptive compression > zstd also supports adaptive compression, compressing as hard as > it can while not impacting I/O speed. So hardware with slow I/O > like a Pi would

Re: Revisiting default initramfs compression

2021-12-08 Thread Michael Hudson-Doyle
On Thu, 9 Dec 2021 at 10:02, Julian Andres Klode wrote: > On Thu, Dec 09, 2021 at 09:21:35AM +1300, Michael Hudson-Doyle wrote: > > On Thu, 9 Dec 2021 at 08:52, Julian Andres Klode < > julian.kl...@canonical.com> > > wrote: > > > > > The most interesting solution would be to create the cpip

Re: Revisiting default initramfs compression

2021-12-08 Thread Julian Andres Klode
On Thu, Dec 09, 2021 at 09:21:35AM +1300, Michael Hudson-Doyle wrote: > On Thu, 9 Dec 2021 at 08:52, Julian Andres Klode > wrote: > > > The most interesting solution would be to create the cpip archive > > dynamically by giving cpio a list of files over a pipe that we create > > dynamically in

Re: Revisiting default initramfs compression

2021-12-08 Thread Michael Hudson-Doyle
On Thu, 9 Dec 2021 at 08:52, Julian Andres Klode wrote: > The most interesting solution would be to create the cpip archive > dynamically by giving cpio a list of files over a pipe that we create > dynamically in the hooks as we copy files in, then pipe that to zstd > --adapt; then it would all

Re: Revisiting default initramfs compression

2021-12-08 Thread Heinrich Schuchardt
On 12/8/21 09:12, Julian Andres Klode wrote: Hi all, some time ago, the default compressor for initramfs was changed from lz4 -9 to zstd -19. This caused significant problems: - it is very slow - it uses a lot of memory The former is a problem for everyone, the latter means that zstd just

Re: Revisiting default initramfs compression

2021-12-08 Thread Julian Andres Klode
On Wed, Dec 08, 2021 at 09:51:44AM -0800, Heinrich Schuchardt wrote: > The memory should only be one factor to be taken into account. The SiFive > Unmatched and the RPi 4 boards both have 8 GiB but slow CPUs. It would be > advisable to use a lower compression level on these. The Pi 4 is limited

Revisiting default initramfs compression

2021-12-08 Thread Julian Andres Klode
Hi all, some time ago, the default compressor for initramfs was changed from lz4 -9 to zstd -19. This caused significant problems: - it is very slow - it uses a lot of memory The former is a problem for everyone, the latter means that zstd just crashes on a Pi Zero. This is an analysis of what

Re: proposed-migration, "SMOOTH_UPDATES", and NBS reports

2021-12-08 Thread Julian Andres Klode
On Wed, Dec 08, 2021 at 05:29:19PM +0100, Sebastien Bacher wrote: > Hey again, > > Le 08/12/2021 à 00:14, Steve Langasek a écrit : > > I expect that with this option set, we will find much fewer problems with > > entanglement of library transitions, and in turn I hope developers will be > > less

Re: proposed-migration, "SMOOTH_UPDATES", and NBS reports

2021-12-08 Thread Sebastien Bacher
Hey again, Le 08/12/2021 à 00:14, Steve Langasek a écrit : I expect that with this option set, we will find much fewer problems with entanglement of library transitions, and in turn I hope developers will be less frustrated by migration delays. Right, I expect that to be the case. It's going to