Re: compression force for zip and ODF files in the installation archives

[Jérôme Bouat]

Hi Thorsten.



I mean there is no benefit for half compression force.> Oh, there's certainly a 
benefit going with the default - it is> considered a sweet spot between achieving 
reasonable compressionn,> while not being excessively slow.

I mean we can accept a slow compression while building the files. Next the 
multiple decompression will have the same speed whatever the compression force 
is (just slightly more memory). It would reduce the installed size for the 
millions downloads each version has :

https://stats.documentfoundation.org/downloads#month,version



Of course, in general nothing against having that configurable in some
ways, perhaps as a hidden config option. Would you be interested
implementing that?


I have no time before a few months.

Regards.

Re: compression force for zip and ODF files in the installation archives

[Thorsten Behrens]

Hi Jérôme, all,

Jérôme Bouat wrote:
> I mean there is no benefit for half compression force.
>
Oh, there's certainly a benefit going with the default - it is
considered a sweet spot between achieving reasonable compressionn,
while not being excessively slow.

Of course, in general nothing against having that configurable in some
ways, perhaps as a hidden config option. Would you be interested
implementing that?

Cheers,

-- Thorsten


signature.asc
Description: PGP signature

compression force for zip and ODF files in the installation archives

[Jérôme Bouat]

Hello.

The building of many ODF files doesn't specify the maximum compression force 
("-9" option), like the below :
"""
zip -qrX --must-match $@ content.xml settings.xml styles.xml 
META-INF/manifest.xml
"""

When I decompress this generated ODF file and compress it again with the 
maximum force, next the file size decreases.

The zip files in share/config doesn't use the maximum force also.

The default zip compression is usually "-6" force. Is there a global option for 
the whole build ? Could we set it to the maximum force ?

I mean there is no benefit for half compression force. Either there is no compression 
("stored" zip method) next the installation archive achieves a better LZX or XZ 
compression with uncompressed data. Or a maximum force with "deflate" zip method ensures 
a lower installation size.